| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Lior Dahan <liord(at)qmasters(dot)co> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, 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:52:31 |
| Message-ID: | CAKFQuwadsLCQq1Ezor2wz4Cr2=Ogv8GNFJoFYof5dPY1TXD0JA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-11-18 14:55:05 | Re: Issues with pg_dump command |
| Previous Message | Bruce Momjian | 2020-11-18 14:52:11 | Re: Issues with pg_dump command |