Re: Incorrect messages emitted from pgoutput when using column lists

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>
Cc: Gunnar Morling <gunnar(dot)morling(at)googlemail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Incorrect messages emitted from pgoutput when using column lists
Date: 2022-11-25 02:53:19
Message-ID: Y4AuHx6ZwGyKll1Z@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Nov 25, 2022 at 02:46:46AM +0000, houzj(dot)fnst(at)fujitsu(dot)com wrote:
> I think the reason is that we didn't filter the column when sending the old
> tuple in pgoutput. We thought that the old tuple won't include columns that not
> in RI, but it seems it will still be null values for such columns in the old
> tuple. So, I think we'd better filter the column for old tuple as well.

Isn't that something where you should have at least some coverage with
one or more regression tests?
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2022-11-25 02:55:44 Re: BUG #17696: Creation of deferrable initially deferred constraint breaks before transaction commit
Previous Message houzj.fnst@fujitsu.com 2022-11-25 02:46:46 RE: Incorrect messages emitted from pgoutput when using column lists