Re: [GENERAL] current postgresql logfile being written to?

> On 22 Jun 2017, at 04:44 , Lucas Possamai wrote: > > > > 2017-06-22 14:16 GMT+12:00 hvjunk >: > >> On 22 Jun 2017, at 4:06 AM, Lucas Possamai > > wrote: >> >> >> >>

Re: [GENERAL] current postgresql logfile being written to?

2017-06-22 14:16 GMT+12:00 hvjunk : > > On 22 Jun 2017, at 4:06 AM, Lucas Possamai wrote: > > > > 2017-06-22 13:54 GMT+12:00 hvjunk : > >> Hi there, >> >> I was hoping for a method (like archive_command) to handle logfile >>

Re: [GENERAL] current postgresql logfile being written to?

> On 22 Jun 2017, at 4:06 AM, Lucas Possamai wrote: > > > > 2017-06-22 13:54 GMT+12:00 hvjunk >: > Hi there, > > I was hoping for a method (like archive_command) to handle logfile > processing/archiving/compression, but

Re: [GENERAL] current postgresql logfile being written to?

2017-06-22 13:54 GMT+12:00 hvjunk : > 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

[GENERAL] current postgresql logfile being written to?

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