Re: Assertion failure with summarize_wal enabled during pg_createsubscriber

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Assertion failure with summarize_wal enabled during pg_createsubscriber
Date: 2024-07-22 15:02:51
Message-ID: CA+TgmoZGEsZodXC4f=XZNkAeyuDmWTSkpkjCEOcF19Am0mt_OA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I went ahead and committed 0001, which is pretty trivial. Hopefully,
at least, it's trivial enough that I didn't mess it up.

Here's a rebase of 0002 and 0003, now 0001 and 0002, with one minor
fix to hopefully avoid annoying CI.

I'm still hoping for some review/feedback/testing of these before I
commit them, but I also don't want to wait too long.

Thanks,

--
Robert Haas
EDB: http://www.enterprisedb.com

Attachment Content-Type Size
v3-0002-Wait-for-WAL-summarization-to-catch-up-before-cre.patch application/octet-stream 19.8 KB
v3-0001-Allow-WAL-summarization-to-back-up-when-timeline-.patch application/octet-stream 3.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2024-07-22 15:10:39 Re: Custom explain options
Previous Message Nathan Bossart 2024-07-22 14:46:29 Re: pg_upgrade and logical replication