magnus, has this fix made it into the 8.2b3 codebase? at least it fixed 1 of
my 3 problems ;-)
regards,
thomas
- Original Message -
From: "Magnus Hagander" <[EMAIL PROTECTED]>
To: "Thomas H." <[EMAIL PROTECTED]>
Sent: Monday, October 30, 2006 1:21 PM
Subject: RE: [BUGS] BUG #2712: cou
It seems to me that it's not been included in b3. Tom?
//Magnus
> -Original Message-
> From: Thomas H. [mailto:[EMAIL PROTECTED]
> Sent: den 8 november 2006 12:59
> To: Magnus Hagander
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #2712: could not fsync segment: Permission
>
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> It seems to me that it's not been included in b3. Tom?
I'm waiting for some report of whether it fixes the problems?
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'ki
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
It seems to me that it's not been included in b3. Tom?
I'm waiting for some report of whether it fixes the problems?
voilà:
Sent: Tuesday, October 31, 2006 7:23 AM
Subject: Re: [BUGS] xlog lockup patch (was: BUG #2712: could not fsync
segment:
This is just to confirm that 8.2 beta3 fixes that problem.
Thanks again,
Jean-Pierre Pelletier
From: Tom Lane <[EMAIL PROTECTED]>
To: "JEAN-PIERRE PELLETIER" <[EMAIL PROTECTED]>
CC: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] ERROR: failed to build any 4-way joins SQL state:
XX000, PostgreSQ
I wrote:
> It might be interesting to think about not requiring the ControlFileLock
> to be held while making new WAL segments. I think the only reason it
> does that is to ensure that link/rename failure can be treated as a hard
> error (because no one could have beat us to the filename), but we'
