Re: propagating replica identity to partitions - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: propagating replica identity to partitions
Date
Msg-id CANP8+j+Uvqzc6-PV3_akO_gAucxm+rFngNkfDz9Uyu9kp2gpbA@mail.gmail.com
Whole thread Raw
In response to Re: propagating replica identity to partitions  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Wed, 20 Feb 2019 at 18:51, Robert Haas <robertmhaas@gmail.com> wrote:

I don't buy Simon's argument that we should treat TABLESPACE
differently because the tables might be really big and take a long
time to move.  I agree that this could well be true, but nobody is
proposing to remove the ability to move tables individually or to use
ONLY here.  Allowing TABLESPACE to recurse just gives people one
additional choice that they don't have today: to move everything at
once. We don't lose any functionality by enabling that.

Doing that would add the single largest footgun in Postgres, given that command's current behavior and the size of partitioned tables.

If it moved partitions concurrently I'd feel differently.

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

pgsql-hackers by date:

Previous
From: Euler Taveira
Date:
Subject: Re: Set fallback_application_name for a walreceiver to cluster_name
Next
From: Tom Lane
Date:
Subject: Re: NOT IN subquery optimization