| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Lior Dahan <liord(at)qmasters(dot)co>, Daniel Gustafsson <daniel(at)yesql(dot)se>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, Jonathan Tauman <JonathanT(at)qmasters(dot)co> |
| Subject: | Re: Issues with pg_dump command |
| Date: | 2020-11-18 14:55:05 |
| Message-ID: | 20201118145505.GC13825@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Nov 18, 2020 at 07:52:31AM -0700, David G. Johnston wrote:
> On Wed, Nov 18, 2020 at 7:44 AM Lior Dahan <liord(at)qmasters(dot)co> wrote:
>
> Is there a way we can tell which tables are under this parent one? Perhaps
> we can dump them instead.
>
>
> The convention here is to inline or bottom-post.
>
> If you don't use declarative partitioning then the specifics of the
> partitioning are buried inside the custom trigger functions that you wrote. If
> you dump triggers, they will show in the pg_dump output, otherwise you will
> have to investigate using other means.
He is on PG 9.6.15, which doesn't support declarative partitioning, so
it must be trigger-based.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jasmine Ng | 2020-11-18 15:42:04 | PostgreSQL 12.4 restore_command in postgresql.auto.conf |
| Previous Message | David G. Johnston | 2020-11-18 14:52:31 | Re: Issues with pg_dump command |