Re: pg_dump is broken for partition tablespaces

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: David Rowley <david(dot)rowley(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-10 16:10:55
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2019-04-10 09:28:21 -0400, Alvaro Herrera wrote:
> So I think that apart from David's patch, we should just document all
> these things carefully.

Yea, I think that's the most important part.

I'm not convinced that we should have any inheriting behaviour btw - it
seems like there's a lot of different ways to think this should behave,
with different good reason each.


Andres Freund

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2019-04-10 16:14:11 Re: Should the docs have a warning about pg_stat_reset()?
Previous Message Andres Freund 2019-04-10 16:09:25 Re: Minimal logical decoding on standbys