Horton

Re: Reopen logfile on SIGHUP

Alexander Kuzmenkov <a.kuzmenkov@postgrespro.ru>

View thread View on postgr.es
From: Alexander Kuzmenkov <a.kuzmenkov@postgrespro.ru>
To: Sergei Kornilov <sk@zsrv.org>, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: "tgl@sss.pgh.pa.us" <tgl@sss.pgh.pa.us>, "robertmhaas@gmail.com" <robertmhaas@gmail.com>, "andres@anarazel.de" <andres@anarazel.de>, "stark@mit.edu" <stark@mit.edu>, "a.lubennikova@postgrespro.ru" <a.lubennikova@postgrespro.ru>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, "g.smolkin@postgrespro.ru" <g.smolkin@postgrespro.ru>
Date: 2018-08-07T13:36:34Z
Lists: pgsql-hackers 
I think the latest v4 patch addresses the concerns raised upthread. I'm 
marking the commitfest entry as RFC.

-- 

Alexander Kuzmenkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

Commits

  1. Implement "pg_ctl logrotate" command