Fujii Masao writes:
> pg_dump allows us to select multiple target tables by using
> multiple -t switches, but pg_restore does not. So, when
> restoring multiple tables, we have to run pg_restore more
> than once as follows. This is a pain to me.
Use the list facilities, options -l and -L.
> Is i
On Tue, Aug 10, 2010 at 11:00 PM, Tom Lane wrote:
> Fujii Masao writes:
>> Is it worth allowing pg_restore to accept multiple -t
>> switches as well as pg_dump?
>
> It's on the TODO list already, no?
Thanks! I found it on the list and understood there are other many
restrictions in pg_restore's
Fujii Masao writes:
> Is it worth allowing pg_restore to accept multiple -t
> switches as well as pg_dump?
It's on the TODO list already, no?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
ht
On Tue, August 10, 2010 13:18, David Fetter wrote:
> On Tue, Aug 10, 2010 at 05:13:22PM +0900, Fujii Masao wrote:
>>
>> Is it worth allowing pg_restore to accept multiple -t
>> switches as well as pg_dump?
>>
>> $ pg_restore -t tbl1 -t tbl2 db.dump
>>
>> Regards,
>
> Yes. :)
>
> What other func
On Tue, Aug 10, 2010 at 05:13:22PM +0900, Fujii Masao wrote:
> Hi,
>
> pg_dump allows us to select multiple target tables by using
> multiple -t switches, but pg_restore does not. So, when
> restoring multiple tables, we have to run pg_restore more
> than once as follows. This is a pain to me.
>
Hi,
pg_dump allows us to select multiple target tables by using
multiple -t switches, but pg_restore does not. So, when
restoring multiple tables, we have to run pg_restore more
than once as follows. This is a pain to me.
$ pg_restore -t tbl1 db.dump
$ pg_restore -t tbl2 db.dump
Is it wo
