Re: [GENERAL] current postgresql logfile being written to?
От | Lucas Possamai |
---|---|
Тема | Re: [GENERAL] current postgresql logfile being written to? |
Дата | |
Msg-id | CAE_gQfVSiCH+pSXFodej3FNhjUh0wMmjAg0H44SgVyT6PW473A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [GENERAL] current postgresql logfile being written to? (hvjunk <hvjunk@gmail.com>) |
Ответы |
Re: [GENERAL] current postgresql logfile being written to?
|
Список | pgsql-general |
2017-06-22 14:16 GMT+12:00 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?
On your postgresql.conf check log_directory. If it's the default, then: /var/log/postgresql
Lucas
В списке pgsql-general по дате отправления: