Re: Feature request: pgdump and version number / -i option
От | Sufficool, Stanley |
---|---|
Тема | Re: Feature request: pgdump and version number / -i option |
Дата | |
Msg-id | C2F174F99918D54CA2A96E57C5079B6FE18663@sbc-exmsg2.sbcounty.gov обсуждение исходный текст |
Ответ на | Re: Feature request: pgdump and version number / -i option ("Dave Page" <dpage@pgadmin.org>) |
Ответы |
Re: Feature request: pgdump and version number / -i option
|
Список | pgadmin-support |
> -----Original Message----- > From: pgadmin-support-owner@postgresql.org > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Dave Page > Sent: Friday, January 09, 2009 1:39 PM > To: Laurent ROCHE > Cc: pgAdmin III support > Subject: Re: [pgadmin-support] Feature request: pgdump and > version number / -i option > > > On Thu, Jan 8, 2009 at 4:05 PM, Laurent ROCHE > <laurent_roche@yahoo.com> wrote: > > > But in a future version, could we have an extra option in > the backup > > popup to use the -i option ? > > This keeps coming back to haunt me in :-(. I've added an > option - hopefully that'll keep everyone happy! Can we get the database to handle this instead / also? If pg_dump / pg_restore were libs, could this be called via pl/pgsql functions instead? SELECT PG_DUMP(database text,schema text, filename text, compressiontype text, other options...)SELECT PG_RESTORE(database text,schema text, filename text) This would not be useable for client side dumps of the database. But in those cases pg_dump could still be used, or the dump location exported/shared. This would also require the dump location to be writeable by the server process (postgres user). > > -- > Dave Page > EnterpriseDB UK: http://www.enterprisedb.com > > -- > Sent via pgadmin-support mailing list > (pgadmin-support@postgresql.org) To make changes to your > subscription: http://www.postgresql.org/mailpref/pgadmin-support >
В списке pgadmin-support по дате отправления: