Re: pg_dump is broken for partition tablespaces

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_dump is broken for partition tablespaces
Date: 2019-04-14 16:10:29
Message-ID: 20190414161029.ojfejg2lexv65m2b@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2019-04-14 10:38:05 -0400, Tom Lane wrote:
> It's entirely possible BTW that this whole business of inheriting
> tablespace from the partitioned table is broken and should be thrown
> out. I certainly don't see any compelling reason for partitions to
> act differently from regular tables in this respect, and the more
> problems we find with the idea, the less attractive it seems.

Indeed. After discovering during the tableam work, and trying to write
tests for the equivalent feature for tableam, I decided that just not
allowing AM specifications for partitioned tables is the right call - at
least until the desired behaviour is clearer. The discussion of the last
few days makes me think so even more.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2019-04-14 16:22:10 Re: Zedstore - compressed in-core columnar storage
Previous Message Laurenz Albe 2019-04-14 15:51:47 Identity columns should own only one sequence