Re: Reopen logfile on SIGHUP

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Reopen logfile on SIGHUP
Дата
Msg-id CA+TgmobqVugbJFoeP=ZiBQ_pA7-710fsuYNtvDv48uzBgRvtQA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Reopen logfile on SIGHUP  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Reopen logfile on SIGHUP  (Alexander Kuzmenkov <a.kuzmenkov@postgrespro.ru>)
Список pgsql-hackers
On Tue, Apr 10, 2018 at 3:17 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> We, as in the core project, are not shipping it.

+1 for what JD said on that subject.

> I'm also unclear
> on why you want to exclude "fix the RPM packaging" as a reasonable
> solution.

Mostly because the complaint was about the *Debian* packaging.  Other
than that, it's possible that that's the way forward.

> It seems likely that some change in that packaging would
> be necessary anyway, as it wouldn't know today about any signaling
> method we might choose to adopt.
>
> Having said that, I'm not averse to providing a solution if it's robust,
> not too invasive and doesn't break other use-cases.  So far we've not
> seen a patch that meets those conditions.

Fair enough.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: Reopen logfile on SIGHUP
Следующее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS