RE: Logical replication initialization time depends dramatically on the publication "schema" size

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: "'Crimean (gmail)'" <crimean(dot)celica(at)gmail(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: RE: Logical replication initialization time depends dramatically on the publication "schema" size
Date: 2026-06-08 12:31:36
Message-ID: OSOPR01MB121530B80714B8807AA05FC61F51C2@OSOPR01MB12153.jpnprd01.prod.outlook.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Dear Crimean,

Thanks for the report. I think the issue has solved by the commit fd7a25a [1],
which is available in upcoming PG19.
Could you please try to test the beta version on your env if possible?

Sadly, we cannot backport the commit to older versions because it must change
the catalog version.

[1]: https://github.com/postgres/postgres/commit/fd7a25af11e2cad4f48ffc4e50f18644e657ed53

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-06-08 16:00:20 Re: Hashed SAOP on composite type with non-hashable column errors at runtime
Previous Message PG Bug reporting form 2026-06-08 11:59:56 BUG #19514: pg_hba error when configuring SSL Replication