Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Why does logical replication launcher exit with exitcode 1? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Why does logical replication launcher exit with exitcode 1?
Date
Msg-id CA+TgmoaEEKT=v6nB4O457SDtcK29hvu==yRADrSyAgqjgDM7eA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Why does logical replication launcher exit with exitcode 1?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Why does logical replication launcher exit with exitcode 1?  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
Tree view 
On Wed, Aug 2, 2017 at 9:33 PM, Peter Eisentraut
<peter.eisentraut@2ndquadrant.com> wrote:
> On 8/2/17 16:52, Robert Haas wrote:
>> I actually don't think it's that unreasonable to get notified when
>> system-wide processes like the autovacuum launcher or the logical
>> replication launcher start or stop.
>
> But we got rid of those start messages recently due to complaints.

Yeah, true.  I'm just talking about what *I* think.  :-)

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

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [HACKERS] foreign table creation and NOT VALID check constraints
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Fix pg_dump's errno checking for zlib I/O