Re: pg_receivewal makes a bad daemon

2021-05-11 Thread Andres Freund
Hi, On 2021-05-07 12:03:36 +0200, Magnus Hagander wrote: > It might be interesting for us as developers, but not to the vast > majority of our users. Most of those get their startup scripts from > our packagers -- so maybe we should encourage packagers to provide it, > like they do for PostgreSQL

Re: pg_receivewal makes a bad daemon

2021-05-11 Thread Andres Freund
Hi, On 2021-05-05 18:34:36 +0200, Magnus Hagander wrote: > Is this really a problem we should fix ourselves? Most daemon-managers > today will happily be configured to automatically restart a daemon on > failure with a single setting since a long time now. E.g. in systemd > (which most linuxen use

Re: pg_receivewal makes a bad daemon

2021-05-11 Thread Peter Eisentraut
On 05.05.21 19:12, Robert Haas wrote: Maybe, but if that's really a non-problem, why does postgres itself restart, and have facilities to write and rotate log files? I think because those were invented at a time when the operating system facilities were less useful. And the log management f

Re: pg_receivewal makes a bad daemon

2021-05-07 Thread Magnus Hagander
On Thu, May 6, 2021 at 5:43 AM Robert Haas wrote: > > On Wed, May 5, 2021 at 10:42 PM David Fetter wrote: > > We do use at least one bit and piece from around the internet to make > > our software usable, namely libreadline, the absence of which make > > psql pretty much unusable. FWIW, we did g

Re: pg_receivewal makes a bad daemon

2021-05-07 Thread Magnus Hagander
On Wed, May 5, 2021 at 7:12 PM Robert Haas wrote: > > On Wed, May 5, 2021 at 12:34 PM Magnus Hagander wrote: > > Is this really a problem we should fix ourselves? Most daemon-managers > > today will happily be configured to automatically restart a daemon on > > failure with a single setting since

Re: pg_receivewal makes a bad daemon

2021-05-05 Thread Robert Haas
On Wed, May 5, 2021 at 10:42 PM David Fetter wrote: > We do use at least one bit and piece from around the internet to make > our software usable, namely libreadline, the absence of which make > psql pretty much unusable. I'm not talking about dependent libraries. We obviously have to depend on s

Re: pg_receivewal makes a bad daemon

2021-05-05 Thread David Fetter
On Wed, May 05, 2021 at 01:12:03PM -0400, Robert Haas wrote: > On Wed, May 5, 2021 at 12:34 PM Magnus Hagander wrote: > > Is this really a problem we should fix ourselves? Most daemon-managers > > today will happily be configured to automatically restart a daemon on > > failure with a single setti

Re: pg_receivewal makes a bad daemon

2021-05-05 Thread Robert Haas
On Wed, May 5, 2021 at 12:34 PM Magnus Hagander wrote: > Is this really a problem we should fix ourselves? Most daemon-managers > today will happily be configured to automatically restart a daemon on > failure with a single setting since a long time now. E.g. in systemd > (which most linuxen uses

Re: pg_receivewal makes a bad daemon

2021-05-05 Thread Magnus Hagander
On Wed, May 5, 2021 at 5:04 PM Robert Haas wrote: > > You might want to use pg_receivewal to save all of your WAL segments > somewhere instead of relying on archive_command. It has, at the least, > the advantage of working on the byte level rather than the segment > level. But it seems to me that

Re: pg_receivewal makes a bad daemon

2021-05-05 Thread Laurenz Albe
On Wed, 2021-05-05 at 11:04 -0400, Robert Haas wrote: > You might want to use pg_receivewal to save all of your WAL segments > somewhere instead of relying on archive_command. It has, at the least, > the advantage of working on the byte level rather than the segment > level. But it seems to me that

pg_receivewal makes a bad daemon

2021-05-05 Thread Robert Haas
You might want to use pg_receivewal to save all of your WAL segments somewhere instead of relying on archive_command. It has, at the least, the advantage of working on the byte level rather than the segment level. But it seems to me that it is not entirely suitable as a substitute for archiving, fo