| From: | Euler Taveira <euler(dot)taveira(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Christopher Baines <mail(at)cbaines(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH] Fix pg_dump --no-tablespaces for the custom format |
| Date: | 2020-05-16 19:44:13 |
| Message-ID: | CAH503wBNETq=RyvMQDxfc48hgW6OcwdvjCfAd++aWzR2u6T2Eg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, 16 May 2020 at 16:31, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> I think (b) would be a break in the archive format, with unclear
> consequences, so I'm not in favor of that.
>
> I came to the same conclusion while inspecting the source code.
--
Euler Taveira http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Gilman | 2020-05-16 20:57:46 | Warn when parallel restoring a custom dump without data offsets |
| Previous Message | Ranier Vilela | 2020-05-16 19:32:46 | Re: Multiple FPI_FOR_HINT for the same block during killing btree index items |