From: | "Ati Rosselet" <ati(dot)rosselet(at)gmail(dot)com> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: again... |
Date: | 2008-10-25 16:35:33 |
Message-ID: | ce6402fc0810250935v1cd207cdld79bd0465c21a9c3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
I wish... no such luck. No virus scanner on the back end (nothing gets on
the server except the database :))
It seems to be a race condition where the old file is closed before the new
file is opened, and the logging attempt fails right at that time. The new
file is created just fine, and from then, until the next 10MB checkpoint,
all is fine. The reason I'm guessing this, is that it doesn't occur at each
file rollover, just sometimes.. indicating (to me at least) that its a
timing problem... I tried to get the code and figure out what its doing..
but.. well... um..not really able to figure it out :(
>
> Maybe you've got a virus scanner that's locking your log files on you?
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2008-10-25 17:09:45 | Re: Question about VACUUM |
Previous Message | Scott Marlowe | 2008-10-25 16:04:01 | Re: again... |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-10-25 16:36:24 | Re: Full socket send buffer prevents cancel, timeout |
Previous Message | Scott Marlowe | 2008-10-25 16:04:01 | Re: again... |