| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Sergey Belyashov <sergey(dot)belyashov(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me> |
| Subject: | Re: BUG #18815: Logical replication worker Segmentation fault |
| Date: | 2025-02-18 22:24:06 |
| Message-ID: | 1773117.1739917446@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
I wrote:
> I don't intend 0003 for back-patch, but the rest of this has to go
> back as far as the bug can be observed, which I didn't test yet.
Ah: this bug is new in v17, because neither brininsertcleanup nor
the whole aminsertcleanup infrastructure exist before that.
So that leaves us with a question of whether 0004 should be
back-patched any further than v17. There's some attraction
to doing so to keep the branches in sync; but there's already
quite a lot of cross-branch churn in worker.c, so on the whole
I'm inclined to just do v17.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2025-02-19 02:28:42 | Re: BUG #18806: When enable_rartitionwise_join is set to ON, the database shuts down abnormally |
| Previous Message | Bruce Momjian | 2025-02-18 20:52:08 | Re: Inconsistency of timezones in postgresql |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2025-02-18 22:28:49 | Re: per backend WAL statistics |
| Previous Message | Jeff Davis | 2025-02-18 22:02:25 | Re: Optimization for lower(), upper(), casefold() functions. |