Re: [GENERAL] current postgresql logfile being written to?
От
hvjunk
Тема
Re: [GENERAL] current postgresql logfile being written to?
Дата
Msg-id
64E38A4F-6501-4757-B213-6A7911305A9B@gmail.com
Ответ на
Re: [GENERAL] current postgresql logfile being written to? (Lucas Possamai)
Список
Дерево обсуждения
[GENERAL] current postgresql logfile being written to? hvjunk <hvjunk@gmail.com>
Re: [GENERAL] current postgresql logfile being written to? Lucas Possamai <drum.lucas@gmail.com>
Re: [GENERAL] current postgresql logfile being written to? hvjunk <hvjunk@gmail.com>
Re: [GENERAL] current postgresql logfile being written to? Lucas Possamai <drum.lucas@gmail.com>
Re: [GENERAL] current postgresql logfile being written to? hvjunk <hvjunk@gmail.com>
On 22 Jun 2017, at 4:06 AM, Lucas Possamai <drum.lucas@gmail.com> wrote:2017-06-22 13:54 GMT+12:00 hvjunk <hvjunk@gmail.com>:Hi there,
I was hoping for a method (like archive_command) to handle logfile processing/archiving/compression, but unless doing it the logrotate way, I don’t see anything that postgresql provides. Is that correct?
The closest I could find is: pg_rotate_logfile()… but here my question is where do I find the current active logfile(s) that postgresql is currently writing to?
(At least that way I can handle all the files that that postgresql is not writing to :) )
HendrikI use logging_collector + log_rotation_age + log_filename + log_min_duration_statement [1]Using those options PG automatically rotates and keep them for a week or more if you specified it.
That I know, but which file is the postgresql server/cluster writing to right now?
В списке pgsql-general по дате отправления
От: Lucas Possamai
Дата:
От: Lucas Possamai
Дата: