| From: | Lewis Kapell <lkapell(at)setonhome(dot)org> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Postgres has stopped logging |
| Date: | 2009-06-05 18:30:17 |
| Message-ID: | 4A296439.40805@setonhome.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
This is a production server, so I'm not going to stop & restart unless
it's really necessary.
Interesting idea about the old log file being deleted. I could still
see the file listed in the directory, though, and could read/edit it.
Thanks for sharing the ideas.
Lewis
Kevin Grittner wrote:
> Lewis Kapell <lkapell(at)setonhome(dot)org> wrote:
>
>> And anyway, there have now been three additional messages written to
>> the log file since it was first created.
>
> As long as it continues to log after you start PostgreSQL with the
> file already in existence, I guess that's not it. You did try a stop
> and a start, and ensure logging still works?
>
>> By changing the log directory, I must have caused the logger
>> process to obtain a new file handle, or something along those lines.
>
> Perhaps you somehow deleted the file while PostgreSQL was still
> running? It would still be linked to the old copy, and would happily
> write to it even though you couldn't see it....
>
> Just brainstorming....
>
> -Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-06-05 18:38:35 | Re: Postgres has stopped logging |
| Previous Message | Kevin Grittner | 2009-06-05 18:26:45 | Re: Postgres has stopped logging |