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 th
I'm still getting a lot of these entries in my eventlog whenever I have a
reasonably large amount of logging:
Event Type:Error
Event Source:PostgreSQL
Event Category:None
Event ID:0
Date:10/22/2008
Time:9:36:28 AM
User:N/A
Computer:--
Description
9, 2008 at 5:11 PM, Alvaro Herrera <[EMAIL PROTECTED]>
wrote:
> Ati Rosselet escribió:
> > sorry, forgot to cc: to the group..To: Alvaro Herrera <
> > [EMAIL PROTECTED]>
> >
> >
> > not as far as I can tell... I have log_destination='stderr'.
Mon, Jun 9, 2008 at 5:11 PM, Alvaro Herrera <[EMAIL PROTECTED]>
wrote:
> Ati Rosselet escribió:
> > sorry, forgot to cc: to the group..To: Alvaro Herrera <
> > [EMAIL PROTECTED]>
> >
> >
> > not as far as I can tell... I have log_destination='std
ueries:))
Thanks.
Ati
On Fri, Jun 6, 2008 at 11:24 PM, Alvaro Herrera <[EMAIL PROTECTED]>
wrote:
> Ati Rosselet escribió:
> > Using postgresql 8.3 on windows 2003 server. I keep seeing this message
> in
> > my system log. Checking the times, it seems to coincide wit
Using postgresql 8.3 on windows 2003 server. I keep seeing this message in
my system log. Checking the times, it seems to coincide with a log
rollover each time, almost as though the db were trying to log something at
precisely the same time as it is closing access to the old file, and before
op
I have several tables with common FKs.. the problem occurs when
performing a large number of inserts on any of the tables at the same
time. The first to start inserting seems to get a lock on the
referenced FK tables and doesn't release them until its done, forcing
the other apps to just wait... a