Re: Retail DDL

From: Thom Brown <thom(at)linux(dot)com>
To: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Retail DDL
Date: 2025-07-24 20:58:00
Message-ID: CAA-aLv6CfcDdPWhra4Lvf53TBzYoT_Kwd1P2qzyb8hfUpPfv0g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 24 Jul 2025 at 21:46, Matheus Alcantara
<matheusssilv97(at)gmail(dot)com> wrote:
>
> On Thu Jul 24, 2025 at 5:26 PM -03, Andrew Dunstan wrote:
> > Some years ago I gave a talk about $subject, but somehow it dropped off
> > my radar. Now I'm looking at it again. The idea is to have a function
> > (or set of functions) that would allow the user to get the DDL for any
> > database object. Obviously we already have some functions for things
> > like views and triggers, but most notably we don't have one for tables,
> > something users have long complained about. I have been trying to think
> > of a reasonable interface for a single function, where we would pass in,
> > say, a catalog oid plus an object oid, and maybe some optional extra
> > arguments. That seems a bit fragile, though. The alternative is that we
> > have a separate function for each object type, e.g.
> > pg_get_{objecttype}_ddl. I'm kinda leaning that way, but I'd like some
> > sort of consensus before any work gets done.
> >
> What about SHOW CREATE TABLE? Some other databases support this syntax.

SHOW is reserved for returning parameters. I don't think we want to
muddy the purpose of that command.

--
Thom Brown
Data Egret (https://dataegret.com)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joel Jacobson 2025-07-24 21:03:27 Re: Optimize LISTEN/NOTIFY
Previous Message Álvaro Herrera 2025-07-24 20:48:34 Re: More protocol.h replacements this time into walsender.c