Re: [HACKERS] logical replication: \dRp+ and "for all tables" - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: [HACKERS] logical replication: \dRp+ and "for all tables"
Date
Msg-id CAMkU=1w=bj5tsSh4PoATF7uPS_-NtE=AEG-SrvggD-ijXk9Pfw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] logical replication: \dRp+ and "for all tables"  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: [HACKERS] logical replication: \dRp+ and "for all tables"  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [HACKERS] logical replication: \dRp+ and "for all tables"  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On Fri, Jun 9, 2017 at 10:20 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
On Sat, Jun 10, 2017 at 7:29 AM, Jeff Janes <jeff.janes@gmail.com> wrote:
> If I create a publication "for all tables", \dRp+ doesn't indicate it is for
> all tables, it just gives a list of the tables.
>
> So it doesn't distinguish between a publication specified to be for all
> tables (which will be dynamic regarding future additions), and one which
> just happens to include all the table which currently exist.
>
> That seems unfortunate.  Should the "for all tables" be included as another
> column in \dRp and \dRp+, or at least as a footnote tag in \dRp+ ?
>

+1. I was thinking the same. Attached patch adds "All Tables" column
to both \dRp and \dRp+.


Looks good to me.  Attached with regression test expected output  changes.

Cheers,

Jeff 
Attachment

pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] logical replication: \dRp+ and "for all tables"
Next
From: Noah Misch
Date:
Subject: [HACKERS] Re: BUG #14680: startup process on standby encounter a deadlock ofTwoPhaseStateLock when redo 2PC xlog