Re: pg_dump is broken for partition tablespaces

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

On 2019-Apr-15, David Rowley wrote:

> To be honest, if I'd done a better job of thinking through the
> implications of this tablespace inheritance in ca4103025d, then I'd
> probably have not bothered submitting a patch for it. We could easily
> revert that, but we'd still be left with the same behaviour in
> partitioned indexes, which is in PG11.

Well, I suppose if we do decide to revert it for tables, we should do it
for both tables and indexes. But as I said, I'm not yet convinced that
this is the best way forward.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-04-15 03:52:19 Re: Adding Unix domain socket path and port to pg_stat_get_wal_senders()
Previous Message Alexander Korotkov 2019-04-15 02:47:55 Re: Status of the table access method work