| From: | Roman Khapov <rkhapov(at)yandex-team(dot)ru> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Additional message in pg_terminate_backend |
| Date: | 2025-12-20 09:26:40 |
| Message-ID: | F6DCC9FF-002B-4CD5-9D36-5C8710142958@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 17 Dec 2025, at 21:02, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
> Greenplum already has support for passing a message in the terminate command
> doesnt it? Or at least it used to have but perhaps it was ripped out, my
> memory is getting a bit fuzzy.
>
> https://github.com/greenplum-db/gpdb-archive/commit/fa6c2d43d675aa05e2d9f797e3008f6fe075ee2c
>
Well, seems like I missed that patch..
Anyway, now I need same functionality in PostgreSQL, and your patch seems interesting,
especially in part where you keep messages in separated shmem region.
So I adopted your patch, maybe in that form it can be useful for PostgreSQL?
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-pg_terminate_backend_msg-and-pg_cancel_backend_ms.patch | application/octet-stream | 16.0 KB |
| unknown_filename | text/plain | 4 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2025-12-20 09:47:11 | Re: Proposal: Conflict log history table for Logical Replication |
| Previous Message | Amit Kapila | 2025-12-20 09:25:15 | Re: Orphaned records in pg_replication_origin_status after subscription drop |