From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Suggested "easy" TODO: pg_dump --from-list |
Date: | 2010-11-24 13:26:08 |
Message-ID: | AANLkTi=adW-XM5_JMrrDaziPj6-BzN2Er9QiYr+POnLu@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hey hackers,
Completely agree with Robert !
It would be nice to dump functions definitions, e.g. to make it possible
keep them in git separately.
I also want to propose to make it possible dump function definitions
as CREATE OR REPLACE FUNCTION rather than just CREATE
FUNCTION (as pg_dump dumps them now). It is would be useful
as well as psql's \ef.
2010/11/24 Robert Haas <robertmhaas(at)gmail(dot)com>
> On Wed, Nov 24, 2010 at 1:15 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Josh Berkus <josh(at)agliodbs(dot)com> writes:
> >>> Well, very little about pg_dump is very [E], IMNSHO. The question in my
> >>> mind here is what format the list file will take
> >
> >> I was thinking same format as pg_restore -l, only without the dumpIDs.
> >
> > Nope ... those strings are just helpful comments, they aren't really
> > guaranteed to be unique identifiers. In any case, it seems unlikely
> > that a user could expect to get the more complicated cases exactly right
> > other than by consulting "pg_dump | pg_restore -l" output. Which makes
> > the use-case kind of dubious to me.
> >
> > I don't say that this wouldn't be a useful feature, but you need a
> > better spec than this.
>
> One thing I've often wished for is the ability to dump a specific
> function (usually right after after I accidentally rm the file the
> source code was in). pg_dump has -t to pick a table, but there's no
> analagous way to select an object that isn't a relation. I think the
> first step here would be to design a system that lets you use a
> command-line argument to dump an arbitrary object, and after that you
> could work on reading the object descriptors from a file rather than
> the command line.
>
> As a first attempt at syntax, I might suggest something along the
> lines of "object type: object name", where the types and names might
> look to COMMENT ON for inspiration.
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
--
// Dmitriy.
From | Date | Subject | |
---|---|---|---|
Next Message | Itagaki Takahiro | 2010-11-24 13:28:08 | Re: Extensions, this time with a patch |
Previous Message | Radosław Smogura | 2010-11-24 13:24:29 | Re: Experimental JDBC driver |