From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Josh Kupershmidt <schmiddy(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: pg_restore multiple --function options |
Date: | 2013-08-26 20:17:34 |
Message-ID: | 20130826201734.GD16776@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Aug 26, 2013 at 10:29:06PM +0300, Heikki Linnakangas wrote:
> Hi,
>
> While looking at the pg_restore code, I noticed that while it
> supports specifying multiple --table options to restore several
> tables, it does not support multiple --function options. Or --index,
> --schema, or --trigger.
>
> The support for multiple --table options was added in 9.3, in
> January. See http://www.postgresql.org/message-id/CAK3UJRG+yV1mK5twLfKVMCwXH4f6PnJou6Rn=ecabyfQH1vVHg@mail.gmail.com.
> Was there a particular reason for only doing it for --table, or was
> it just an oversight or lack of interest? No doubt that --table is
> the most interesting one, but IMHO the other options should behave
> the same, for the sake of consistency.
+1 for making them consistent. There will also be an improvement in
usability.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-08-26 20:31:21 | Re: GetTransactionSnapshot() in enum.c |
Previous Message | Pavel Stehule | 2013-08-26 20:10:47 | Re: Improving avg performance for numeric |