From: Tom Lane <tgl@sss.pgh.pa.us>
To: "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>
cc: Amit Kapila <amit.kapila16@gmail.com>,
        "396934406@qq.com" <396934406@qq.com>,
        pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: pg15 beta2 bug:cause by logcial replation
In-reply-to: 
 <OS0PR01MB571689015E31F1AF1784350094BD9@OS0PR01MB5716.jpnprd01.prod.outlook.com>
References: <tencent_30262B030A662CC2DC8FF5D252C00D514B09@qq.com>
 <OS0PR01MB571689015E31F1AF1784350094BD9@OS0PR01MB5716.jpnprd01.prod.outlook.com>
Comments: In-reply-to "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>
	message dated "Fri, 01 Jul 2022 04:09:22 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <568156.1656652619.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 01 Jul 2022 01:16:59 -0400
Message-ID: <568157.1656652619@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/568157.1656652619%40sss.pgh.pa.us>
Precedence: bulk

"houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com> writes:
> On Friday, July 1, 2022 11:35 AM 396934406@qq.com <396934406@qq.com>  wr=
ote:
>> ERROR:  could not receive list of replicated tables from the publisher:=
 ERROR:  column t.attnames does not exist
>> LINE 2: , t.attnames

> Just to confirm, did you use the PG15 beta1 or earlier PG15 version
> as the publisher and use PG15 beta2 as the subscriber ?

It looks to me like this was an attempt to replicate from 15beta1 to
15beta2, which would fail because commit fd0b9dceb imagines that any
server reporting version >=3D 15 will have pg_publication_tables.attnames,
even though that column was not there in beta1.

I bitched about the ill-timing of that schema change at the time
but was outvoted.  At this point I think it's water over the dam.
We could perhaps change that test in fetch_table_list(), but it'd
require access to the source server's catversion, which I don't think
is readily available.  In any case, by the time we could provide a fix
it'd be useless to testers of beta1; they'd have updated already by
some other method.

			regards, tom lane