On Monday 24 November 2008 23:37:02 Barry Reddy wrote:
> Can anyone clarify if this apparent contradiction is an oversight ? Old
> documentation with new archiving documentation patched on, with no
> attention paid to the seeming contradiction on guidelines for filesystem
> backups of a running PG
In response to "Barry Reddy" <[EMAIL PROTECTED]>:
>
> The following bug has been logged online:
>
> Bug reference: 4548
> Logged by: Barry Reddy
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3.3
> Operating system: Linux 2.6.24-19-server i686 RHEL5
> Description:
The following bug has been logged online:
Bug reference: 4548
Logged by: Barry Reddy
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: Linux 2.6.24-19-server i686 RHEL5
Description:Documentation Contradiction for 8.3
Details:
I’ve been goi
Alexandra Nitzschke wrote:
BTW... how about a block checksum that is checked just before writing
a block and just after reading it? I know this would degrade
performance, but I think we can afford that. Would it be possible to
incorporate such code without having to do too much patching?
ora
Bug reference: 4543
Logged by: Tzvi R.
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.5
Operating system: Linux (kernel 2.6.18)
Description:File references are still held to deleted files
Details:
Hi,
We frequently create large work tables that span across m
Hi,
first of all I would like to thank you for all your efforts.
> We really need a test case.
unfortunately this kind of bugs tend to be non-reproducable. I assume that there is a race condition which is only hit
in rare cases, under heavy load and when mars and venus are exactly aligned... ;
Yes, of course.
After we started up the copied database, the system runs withour error for two
days.
That means some recordsets has been inserted sucessfully already.
Gregory Stark schrieb:
Alexandra Nitzschke <[EMAIL PROTECTED]> writes:
This monday I updated postgres to 8.3.5 on the standb
We had the same problem last week when installing PG 8.3.5/8.3.4 on two
machine running Win2k3 Server sr2 belonging to one of our customers.
After some hours of trial and error we found out that this error only
occurred when not installing to the system drive. If we chose the system
drive for insta
