From: | Jessica Richard <rjessil(at)yahoo(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Postgres log file |
Date: | 2010-10-15 18:03:12 |
Message-ID: | 165713.55278.qm@web111313.mail.gq1.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
I am curious about this scenario:
What is going to happen when a server is running and the Postgres log file is
accidentally deleted or renamed? The server will have no place to write its log
entries obviously.. what else?.
Is there any way to check within Postgres what the current log name (with a
particular time stamp when rotated last time) is so that a file with a correct
matching name can be manually created?
For this situation, what is the proper way to get the server to write to a new
log file without having to bounce the Postgres server itself?
Thanks!
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Capobianco | 2010-10-15 18:13:49 | Re: oracle to psql migration - slow query in postgres |
Previous Message | Igor Neyman | 2010-10-15 17:43:40 | Re: oracle to psql migration - slow query in postgres |
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Capobianco | 2010-10-15 18:13:49 | Re: oracle to psql migration - slow query in postgres |
Previous Message | Igor Neyman | 2010-10-15 17:43:40 | Re: oracle to psql migration - slow query in postgres |