pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: 396934406@qq.com <396934406@qq.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
Cc: Amit Kapila <amit.kapila16@gmail.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: Re: pg15 beta2 bug:cause by logcial replation
Date: Fri, 1 Jul 2022 14:43:45 +0800
Message-ID: <tencent_55711625EE6D7ABE290E862525EB956B0508@qq.com> (raw)
References: <tencent_30262B030A662CC2DC8FF5D252C00D514B09@qq.com>
	<OS0PR01MB571689015E31F1AF1784350094BD9@OS0PR01MB5716.jpnprd01.prod.outlook.com>
	<568157.1656652619@sss.pgh.pa.us>

Obviously in the same pg server pg15 beta2, because my 
subscriber creation use "create_slot='false'", another clue is i use "\c", all the test on the same cluster.


396934406@qq.com
 
From: Tom Lane
Date: 2022-07-01 13:16
To: houzj.fnst@fujitsu.com
CC: Amit Kapila; 396934406@qq.com; pgsql-bugs
Subject: Re: pg15 beta2 bug:cause by logcial replation
"houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com> writes:
> On Friday, July 1, 2022 11:35 AM 396934406@qq.com <396934406@qq.com>  wrote:
>> 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 >= 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
 


view thread (8+ messages)  latest in thread

Message-ID: <tencent_55711625EE6D7ABE290E862525EB956B0508@qq.com>
Permalink:  ../tencent_55711625EE6D7ABE290E862525EB956B0508@qq.com/
Also on:    postgresql.org/message-id/tencent_55711625EE6D7ABE290E862525EB956B0508@qq.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: 396934406@qq.com, tgl@sss.pgh.pa.us, houzj.fnst@fujitsu.com, amit.kapila16@gmail.com
  Subject: Re: pg15 beta2 bug:cause by logcial replation
  In-Reply-To: <tencent_55711625EE6D7ABE290E862525EB956B0508@qq.com>
  References: <tencent_30262B030A662CC2DC8FF5D252C00D514B09@qq.com> <OS0PR01MB571689015E31F1AF1784350094BD9@OS0PR01MB5716.jpnprd01.prod.outlook.com> <568157.1656652619@sss.pgh.pa.us> <tencent_55711625EE6D7ABE290E862525EB956B0508@qq.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox