Re: logical replication: \dRp+ and "for all tables"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: logical replication: \dRp+ and "for all tables"
Date: 2017-06-10 14:42:25
Message-ID: 23001.1497105745@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> On Fri, Jun 9, 2017 at 10:20 PM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
> wrote:
>> On Sat, Jun 10, 2017 at 7:29 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>>> 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.

This patch confuses me. In the first place, I don't see the argument for
adding the "all tables" property to \dRp output; it seems out of place
there. In the second place, this really fails to respond to what I'd call
the main usability problem with \dRp+, which is that the all-tables
property is likely to lead to an unreadably bulky list of affected tables.
What I'd say the patch ought to do is *replace* \dRp+'s list of affected
tables with a notation like "(all tables)" when puballtables is true.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2017-06-10 18:04:19 Re: PostgreSQL 10 changes in exclusion constraints - did something change? CASE WHEN behavior oddity
Previous Message Alvaro Herrera 2017-06-10 13:13:32 Re: PG10 transition tables, wCTEs and multiple operations on the same table