Re: 8.3 RC1 - Logging and filenames
| От | Andy Shellam |
|---|---|
| Тема | Re: 8.3 RC1 - Logging and filenames |
| Дата | |
| Msg-id | 33671a790801120818i31f126b9ueac31f33ddb23063@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: 8.3 RC1 - Logging and filenames (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: 8.3 RC1 - Logging and filenames
|
| Список | pgsql-admin |
Hi all,
But surely if the rotation is disabled, PostgreSQL will just append to the log if it exists (hence the extra option of "truncate on rotation?")
Many services use a single log file and just keep adding to it - that's the way I'd prefer to set PostgreSQL up, simply so I can predict what the log file's name is. Our rotation system will then rotate the log and keep the name in the same format as all our other services.
Andy
But surely if the rotation is disabled, PostgreSQL will just append to the log if it exists (hence the extra option of "truncate on rotation?")
Many services use a single log file and just keep adding to it - that's the way I'd prefer to set PostgreSQL up, simply so I can predict what the log file's name is. Our rotation system will then rotate the log and keep the name in the same format as all our other services.
Andy
On 1/11/08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Joshua D. Drake" <jd@commandprompt.com> writes:
> Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> You don't really have any choice about the matter --- Postgres will
>> not use a single fixed filename because that would be guaranteed to
>> lose log entries across a rotation.
> Unless he is using syslog?
True, if you really dislike the way that the built-in log collector
works, syslog is probably your best alternative.
regards, tom lane
В списке pgsql-admin по дате отправления: