My case is that a backend was holding the file open. It was not some other=
unhelpful program. That's why I had to write a program that held the file=
open with the same flags that postgres uses (including FILE_SHARE_DELETE).
We have a process that wrote to the DB, and then for many days it only read=
from the DB, so it didn't move on to another WAL file.
-Luke
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Wednesday, September 09, 2009 3:20 PM
> To: Luke Koops
> Cc: Heikki Linnakangas; pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #5038: WAL file is pending deletion
> in pg_xlog folder, this interferes with WAL archiving.
>
> Luke Koops <luke.koops@entrust.com> writes:
> > Heikki is proposing that the file be renamed before
> it is first deleted.
>
> Indeed, and what I'm saying is that that will still fail if
> some unhelpful program is holding the file open without
> FILE_SHARE_DELETE.
> Which is what I understood your case to be ...
>
> regards, tom lane
>
