Re: BUG #18815: Logical replication worker Segmentation fault
От | Sergey Belyashov |
---|---|
Тема | Re: BUG #18815: Logical replication worker Segmentation fault |
Дата | |
Msg-id | CAOe0RDxj6QCBHzKY_OGoLHykJ7oAYx2SD_dKs8_aeNBk9WTTXA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #18815: Logical replication worker Segmentation fault (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #18815: Logical replication worker Segmentation fault
Re: BUG #18815: Logical replication worker Segmentation fault |
Список | pgsql-hackers |
Hi, The 4th patch is not applicable for the current REL_17_STABLE branch. There are a lot of differences from master in the worker.c. Best regards, Sergey Belyashov ср, 19 февр. 2025 г. в 01:24, Tom Lane <tgl@sss.pgh.pa.us>: > > 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
В списке pgsql-hackers по дате отправления: