Re: [HACKERS] Why does logical replication launcher exit with exitcode 1?
От | Andres Freund |
---|---|
Тема | Re: [HACKERS] Why does logical replication launcher exit with exitcode 1? |
Дата | |
Msg-id | 20170801230303.n6u67hmqwudxuyjv@alap3.anarazel.de обсуждение исходный текст |
Ответ на | [HACKERS] Why does logical replication launcher exit with exit code 1? (Thomas Munro <thomas.munro@enterprisedb.com>) |
Ответы |
Re: [HACKERS] Why does logical replication launcher exit with exitcode 1?
Re: [HACKERS] Why does logical replication launcher exit with exitcode 1? Re: [HACKERS] Why does logical replication launcher exit with exitcode 1? |
Список | pgsql-hackers |
Hi, On 2017-08-02 10:58:32 +1200, Thomas Munro wrote: > When I shut down a cluster that isn't using logical replication, it > always logs a line like the following. So do the build farm members I > looked at. I didn't see anything about this in the open items list -- > isn't it a bug? > > 2017-08-02 10:39:25.007 NZST [34781] LOG: worker process: logical > replication launcher (PID 34788) exited with exit code 1 Exit code 0 signals that a worker should be restarted. Therefore graceful exit can't really use that. I think a) we really need to improve bgworker infrastructure around that b) shows the limit of using bgworkers for this kinda thing - we should probably have a more bgworker like infrastructure for internal workers. - Andres
В списке pgsql-hackers по дате отправления: