| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_receivewal and SIGTERM |
| Date: | 2022-08-22 14:05:16 |
| Message-ID: | YwONHOxDOMpLLI5B@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: Michael Paquier
> While looking at the last patch proposed, it strikes me that
> time_to_stop should be sig_atomic_t in pg_receivewal.c, as the safe
> type of variable to set in a signal handler. We could change that,
> while on it..
Done in the attached patch.
> Backpatching this stuff is not an issue here.
Do you mean it can, or can not be backpatched? (I'd argue for
backpatching since the behaviour is slightly broken at the moment.)
Christoph
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-pg_receivewal-pg_recvlogical-Exit-cleanly-on-SIGTERM.patch | text/x-diff | 4.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2022-08-22 14:05:43 | Re: Schema variables - new implementation for Postgres 15 |
| Previous Message | Andrew Dunstan | 2022-08-22 13:44:42 | Re: Supporting TAP tests with MSVC and Windows |