From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Suggested "easy" TODO: pg_dump --from-list |
Date: | 2010-11-24 14:00:35 |
Message-ID: | AANLkTin-8QGW-p5euFNFM80s1GyCTYWHJCi2Oayj+3jZ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Nov 24, 2010 at 8:41 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> On 11/24/2010 07:29 AM, Robert Haas wrote:
>> 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.
>
> pg_dump already uses a list of object types (e.g. as seen in the output from
> pg_restore --list). Let's not invent something new if we don't need to. But
> we'll need more than that. We'll need enough for disambiguation, especially
> for functions which is your stated use case. So, something like this might
> work:
>
> FUNCTION:myschema.myfunc:integer,text,timestamp with time zone
Actually, that's pretty much exactly what I was proposing, except that
I would've kept the existing convention for how to write a function's
arguments:
FUNCTION:myschema.myfunc(integer,text,timestamp with time zone)
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Joachim Wieland | 2010-11-24 14:05:16 | Re: Suggested "easy" TODO: pg_dump --from-list |
Previous Message | Andrew Dunstan | 2010-11-24 13:41:36 | Re: Suggested "easy" TODO: pg_dump --from-list |