From: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Ziga <ziga(at)ljudmila(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Retail DDL |
Date: | 2025-08-16 05:08:28 |
Message-ID: | CALdSSPh8QeDfDt9Ap5vaZytHafBzXMgNjEM7nDKj465UvROppw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi!
On Thu, 14 Aug 2025 at 23:30, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> Interesting. I think there are good reasons to have this as builtin
> functions, though, not least that it would allow us to base some psql
> meta-commands on it, or possibly an SQL command (DESCRIBE ?).
DESCRIBE would be confusing with extended protocol Describe message,
used for prepared statements and portals. At least for me this would
be confusing.
> Builtin
> functions are also likely to be faster.
We are not actually aiming for speed here, aren’t we?
Overall, Im +1 on `pg_get_{objecttype}_ddl` or maybe
`pg_show_{objecttype}_ddl` design.
--
Best regards,
Kirill Reshke
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2025-08-16 05:56:27 | Re: Raw parse tree is not dumped to log |
Previous Message | Thomas Munro | 2025-08-16 03:37:33 | Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock |