The filename includes date, but not time, because that is how the
relevant options are set up in the configuration file. I could have
specified that the file name also include hour, minute and second, but
that should make no difference.
And anyway, there have now been three additional messages written to the
log file since it was first created. So the fact that the file already
exists doesn't seem to be the root of the problem.
I can only guess that there was some glitch in the operating system I/O
functions. By changing the log directory, I must have caused the logger
process to obtain a new file handle, or something along those lines.
Thank you,
Lewis Kapell
Computer Operations
Seton Home Study School
-------------------------------------------------------
For a free subscription to the Seton Home Study School monthly
electronic newsletter, send an e-mail to newsletter-sub@xxxxxxxxxxxxx
-------------------------------------------------------
Kevin Grittner wrote:
Lewis Kapell <lkapell@xxxxxxxxxxxxx> wrote:
So my problem is solved, although I wish I had some idea what had
caused it in the first place.
Just a wild shot in the dark -- does it not behave well if the file
already exists? I noticed that your filename includes date but not
time. Perhaps time healed this wound by moving on to a new date?
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
