RE: BUG #19041: Logical replication locks wal processing - Mailing list pgsql-bugs

From Hayato Kuroda (Fujitsu)
Subject RE: BUG #19041: Logical replication locks wal processing
Date
Msg-id OSCPR01MB14966D4A18673FB3D481ED5E8F503A@OSCPR01MB14966.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: BUG #19041: Logical replication locks wal processing  (Sergey Belyashov <sergey.belyashov@gmail.com>)
List pgsql-bugs
Dear Sergey,

> Thank you for your explanation. It is what I'm about.
> Is it possible to optimize something to prevent decoding the whole WAL
> if there are no affected tables there?

I recalled there was a proposal which skips decoding changes for unpublished
tables, but it was withdrawn [1]. One of reasons was that a new transaction must
be started to check whether the table must be published or not, thus the
performance can be degraded in some cases.

I have also considered Dilip's idea [2] once, but it needs some architectural
changes. I cannot find on-going thread neither.

[1]: https://commitfest.postgresql.org/patch/5585/
[2]: https://www.postgresql.org/message-id/CAFiTN-uwgQ%3DHVFRdz2%3DJUVgQHCPubatKrK14xD-0Ov71HRpbTQ%40mail.gmail.com

Best regards,
Hayato Kuroda
FUJITSU LIMITED


pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
Next
From: Alexander Lakhin
Date:
Subject: Re: BUG #19037: Planner fails on estimating array length with "no relation entry" error