Skip site navigation (1) Skip section navigation (2)

Re: BUG #2712: could not fsync segment: Permission

From: "Thomas H(dot)" <me(at)alternize(dot)com>
To: "Magnus Hagander" <mha(at)sollentuna(dot)net>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #2712: could not fsync segment: Permission
Date: 2006-11-08 14:48:07
Message-ID: 067901c70344$e7d824b0$0201a8c0@iwing (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
> "Magnus Hagander" <mha(at)sollentuna(dot)net> 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: Permission)
> i've loaded 1gb of data without any xlog-problems, whereas with the 8.2b2
> executable it locked up after ~100mb. the xlog-files are cycling...
> if i need to test for some specific behaviour let me know.

after using the patched b2 executable, the db system never locked up again, 
and no xlog error messages in the logs either.

the other problem with locked files within the data directories is 
unaffected by the patch, obviously - but as that does not lock up the 
system, its not that severe (but still scary ;-))


In response to

pgsql-bugs by date

Next:From: JEAN-PIERRE PELLETIERDate: 2006-11-08 15:00:57
Subject: Re: ERROR: failed to build any 4-way joins SQL state: XX000, PostgreSQL
Previous:From: Tom LaneDate: 2006-11-08 14:42:06
Subject: Re: BUG #2712: could not fsync segment: Permission

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group