Re: 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.


maybe a similar patch could be found for the 2nd permission problem, where
the writer process tries to use a previously deleted file whose filehandle
is still in use by another postgresql process:

2006-10-31 07:12:37 [5392] ERROR:  42501: could not open relation
1663/3964774/6696548: Permission denied
2006-10-31 07:12:37 [5392] LOCATION:  mdopen, md.c:366
2006-10-31 07:12:38 [5392] ERROR:  42501: could not open relation
1663/3964774/6696548: Permission denied
2006-10-31 07:12:38 [5392] LOCATION:  mdopen, md.c:366


thanks for your efforts, very much appreciated!

- thomas

----- Original Message -----
Sent: Sunday, October 29, 2006 6:10 PM
Subject: Re: [BUGS] BUG #2712: could not fsync segment: Permission


> > I haven't reproduced this on my box. But if you can give me
> a patch to
> > try I can build binaries for Thomas to test, if he can do
> testing but
> > not building.
>
> Utterly untested ... BTW, why does pgrename have an #if to
> check either GetLastError() or errno, but pgunlink doesn't?

Ok, I've built a .EXE with this patch. It's compiled without pretty much
all other options, hope that still works :-) (Meaning no NLS, no
kerberos, no SSL etc)

Grab the exe from
http://www.hagander.net/download/postgres_renamepatch.zip.

Sorry about the delay.

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match