From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Simon Riggs <simon@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: propagating replica identity to partitions
Date: Fri, 29 Mar 2019 10:51:33 +0100
Message-ID: <260477b8-ba7e-b0c2-580e-735bdd6e9591@2ndquadrant.com> (raw)
In-Reply-To: <CANP8+jJn5Ws-pMN_n5U-8TCZSy9_2CQKT2UFSuswDHQ6C5Lu3A@mail.gmail.com>
References: <20190323013354.GI20584@paquier.xyz>
<806fd173-9084-5fb8-ed78-25398ab9e92f@2ndquadrant.com>
<20190328164633.GA22571@alvherre.pgsql>
<CANP8+jJn5Ws-pMN_n5U-8TCZSy9_2CQKT2UFSuswDHQ6C5Lu3A@mail.gmail.com>
On 2019-03-28 18:16, Simon Riggs wrote:
> SET TABLESPACE should not recurse because it copies the data, while
> holding long locks. If that was ever fixed so it happened concurrently,
> I would agree this could recurse by default.
Since a partitioned table has no storage, what is the meaning of moving
a partitioned table to a different tablespace without recursing?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, simon@2ndquadrant.com, alvherre@2ndquadrant.com, michael@paquier.xyz, robertmhaas@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: propagating replica identity to partitions
In-Reply-To: <260477b8-ba7e-b0c2-580e-735bdd6e9591@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox