Re: Better error message for unsupported replication cases

2022-02-14 Thread Tom Lane
Amit Kapila writes: > On Tue, Feb 15, 2022 at 3:42 AM Tom Lane wrote: >> ... Maybe the error message >> could be bikeshedded ... is "non-table relation" terminology >> that we use in user-facing messages? > The other option could be "logical replication source relation > \"%s.%s\" is not a tabl

Re: Better error message for unsupported replication cases

2022-02-14 Thread Amit Kapila
On Tue, Feb 15, 2022 at 3:42 AM Tom Lane wrote: > > In [1] there's a complaint that if you try to logically replicate > a partitioned table from v13-or-later to v12-or-earlier, you get > "table XXX not found on publisher", which is pretty confusing > because the publisher certainly does have such

Better error message for unsupported replication cases

2022-02-14 Thread Tom Lane
In [1] there's a complaint that if you try to logically replicate a partitioned table from v13-or-later to v12-or-earlier, you get "table XXX not found on publisher", which is pretty confusing because the publisher certainly does have such a table. That happens because fetch_remote_table_info is t