Re: propagating replica identity to partitions

On 2019-Feb-20, Robert Haas wrote:

> On Wed, Feb 20, 2019 at 12:38 PM Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:

> > Maybe the ALL IN TABLESPACE and OWNED BY sub-forms should be split to a
> > separate para. I suggest:
> >
> > : This form changes the table's tablespace to the specified tablespace
> > : and moves the data file(s) associated with the table to the new
> > : tablespace. Indexes on the table, if any, are not moved; but they
> > : can be moved separately with additional SET TABLESPACE commands.
> > : When applied to a partitioned table, nothing is moved, but any
> > : partitions created afterwards with CREATE TABLE PARTITION OF
> > : will use that tablespace.
> > :
> > : All
> > : tables in the current database in a tablespace can be moved by using
> > : the ALL IN TABLESPACE form, which will lock all tables to be moved
> > : first and then move each one. This form also supports OWNED BY,
> > : which will only move tables owned by the roles specified. If the
> > : NOWAIT option is specified then the command will fail if it is
> > : unable to acquire all of the locks required immediately. Note that
> > : system catalogs are not moved by this command, use ALTER DATABASE or
> > : explicit ALTER TABLE invocations instead if desired. The
> > : information_schema relations are not considered part of the system
> > : catalogs and will be moved. See also CREATE TABLESPACE.
>
> Seems reasonable.

Pushed this bit, thanks.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services