Yes, sometimes the logs recycle just fine, but other times not.
Sometimes I get an FATAL 2 ERROR because postgresql appears to
be trying to write to a log file, that returns a permission denied
error.
So something isn't working properly.
I ran a little test yesterday though. I wrote a bit of code that
spawned 4 threads that all insert and update into the same table
at the same time. I did 5 million inserts and updates on the
same table and it worked just fine. I watched the postmaster.log
file and it recycled a log file about every 5-10 minutes.
I am starting to think that the problem my not be with the database,
but with cygwin and windows 2000
Dima Tkach <dmitry@openratings.com> wrote ..
> So, where is the problem? You said they are *not* recycled, but the
> messages you quoted say that they *are* :-)
> Besides, it's not an error, but just what it says - a DEBUG message.
> In two words - you are OK. There is no problem here, it works just fine.
>
> Dima
>
> Colin Mangiagalli wrote:
> > Hi
> >
> > I previously had a problem with the transaction logs not being recycled
> > properly with the following configuration:
> >
> > PostgreSQL 7.2.1-2
> > cygwin dll 1.3.12-2
> > ipc 1.11-1
> >
> > The error was as follows:
> >
> > DEBUG: recycled transaction log file 0000000400000015
> > DEBUG: recycled transaction log file 0000000400000016
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 3: if posting/reading through Usenet, please send an appropriate
> > subscribe-nomail command to majordomo@postgresql.org so that your
> > message can get through to the mailing list cleanly
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
