| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Kirk Wolak <wolakk(at)gmail(dot)com> |
| Cc: | Jelte Fennema <postgres(at)jeltef(dot)nl>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Adding SHOW CREATE TABLE |
| Date: | 2023-06-01 20:46:07 |
| Message-ID: | 895df15a-3d11-92e0-a420-290a6d34634a@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 2023-06-01 Th 16:39, Kirk Wolak wrote:
> On Thu, Jun 1, 2023 at 3:13 PM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> On 2023-06-01 Th 12:57, Kirk Wolak wrote:
>
>> PS: It dawned on me that if pg_dump had used server side code to
>> generate its DDL, its complexity would drop.
>
> Maybe, that remains to be seen. pg_dump needs to produce SQL that
> is suitable for the target database, not the source database.
>
>
> First, pg_dump has some special needs in addressing how it creates
> tables, to be able to load the data BEFORE indexing, and constraining
> (lest you have to struggle with dependencies of FKs, etc etc)...
>
> But version checking is interesting... Because I found no way to tell
> pg_dump what DB to target.
>
The target version is implicitly the version it's built from.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wen Yi | 2023-06-02 00:47:17 | [Beginner Question]A question about yacc & lex |
| Previous Message | Kirk Wolak | 2023-06-01 20:39:14 | Re: Adding SHOW CREATE TABLE |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tristan Partin | 2023-06-01 21:16:27 | Re: [PATCH] Missing dep on Catalog.pm in meson rules |
| Previous Message | Kirk Wolak | 2023-06-01 20:39:14 | Re: Adding SHOW CREATE TABLE |