| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| 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 13:28:21 |
| Message-ID: | 20190410132821.GA23319@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Apr-09, Alvaro Herrera wrote:
> There is one deficiency that needs to be solved in order for this to
> work fully: currently there is no way to reset "reltablespace" to 0.
Actually, there is one -- just need to
ALTER TABLE .. SET TABLESPACE <the database default tablespace>
this took me a bit by surprise, but actually it's quite expected.
So I think that apart from David's patch, we should just document all
these things carefully.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2019-04-10 14:22:38 | Re: block-level incremental backup |
| Previous Message | Fred .Flintstone | 2019-04-10 13:15:13 | Re: PostgreSQL pollutes the file system |