Re: ALTER PUBLICATION materializing the list of tables

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER PUBLICATION materializing the list of tables
Date: 2017-05-24 23:28:26
Message-ID: f9ff23c6-b3bd-8bff-4d10-140c3e0a99da@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 5/22/17 18:08, Jeff Janes wrote:
> If I create a publication FOR ALL TABLES and then change my mind, the
> only thing I can do is drop the publication and recreate it.
>
> Since "ALTER PUBLICATION name SET TABLE" allows you to replace the
> entire table list, shouldn't it also let you change from the dynamic FOR
> ALL TABLES to a static specific list?

I would file this under "anything is possible, but not everything is
worthwhile".

The purpose of the ADD/SET TABLE clauses is that be able to add new
tables that are related to the tables you are already publishing (e.g.,
new partitions). If you are already publishing all tables
automatically, then there is no reason for replacing that with a list of
specific tables. You can also just add a new publication and add that
to the subscription.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-05-24 23:31:31 Re: Create subscription with `create_slot=false` and incorrect slot name
Previous Message Peter Eisentraut 2017-05-24 23:24:08 Re: ALTER PUBLICATION documentation