| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de>, soni de <soni(dot)de(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Regarding pg_dump utility |
| Date: | 2006-06-08 16:38:38 |
| Message-ID: | 20060608163838.GF17421@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Jim C. Nasby wrote:
> On Thu, Jun 08, 2006 at 06:33:28PM +0200, Andreas Pflug wrote:
> > Alvaro Herrera wrote:
> >
> > >
> > >
> > >Personally I think it would be neat. For example the admin-tool guys
> > >would be able to get a dump without invoking an external program.
> > >Second it would really be independent of core releases (other than being
> > >tied to the output format.) pg_dump would be just a simple caller of
> > >such a library, and anyone else would be able to get dumps easily, in
> > >whatever format.
> >
> > pgAdmin currently invokes pg_dump/restore externally with pipes attached
> > to stdin/out/err, but a library implementation would solve some
> > headaches (esp. concerning portability) managing background
> > execution/GUI updates/process control. I'd like a libpgdumprestore
> > library, with pg_dump/pg_restore being lean wrapper programs.
>
> Would a pg_dumpall library also make sense?
One would think that libpgdump should take care of this as well ...
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Pflug | 2006-06-08 16:42:25 | Re: JOIN with inherited table ignores indexes |
| Previous Message | Jim C. Nasby | 2006-06-08 16:35:01 | Re: Regarding pg_dump utility |