Re: SHOW CREATE

From: David Fetter <david(at)fetter(dot)org>
To: Michael Glaesemann <grzm(at)seespotcode(dot)net>
Cc: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: SHOW CREATE
Date: 2019-07-14 00:34:40
Message-ID: 20190714003440.GR24679@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jul 13, 2019 at 06:32:41PM -0500, Michael Glaesemann wrote:
>
>
> > On 2019–07–05, at 12:14, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> wrote:
> >
> > In doing that work, it became clear that the command was serving two masters:
> > 1. A desire to see the underlying nuts and bolts of a given database object.
> > 2. A desire to essentially make the schema portion of pg_dump a server side command.
> >
> > To that end, I see splitting this into two commands, SHOW CREATE
> > and SHOW DUMP.
>
> I like the idea of having these features available via SQL as
> opposed to separate tools. Is it necessary to have specific commands
> for them? It seems they would potentially more useful as functions,
> where they'd be available for all of the programmatic features of
> the rest of SQL.

Having commands for them would help meet people's expectations coming
from other RDBMSs.

On the other hand, making functions could just be done in SQL, which
might hurry the process along.

Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-07-14 01:47:59 Re: Conflict handling for COPY FROM
Previous Message Tomas Vondra 2019-07-13 23:44:52 Re: Avoiding hash join batch explosions with extreme skew and weird stats