Re: pg_dump(all) library - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pg_dump(all) library
Date
Msg-id 488B6270.9040408@dunslane.net
Whole thread Raw
In response to Re: pg_dump(all) library  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers

Joshua D. Drake wrote:
>
> It seems to be that quite a bit of pg_dumps functionality could be 
> pushed into PostgreSQL as functions. This would end up defining an API 
> on its own.
>
> pg_dump the executable would just be a shell that calls the functions 
> in appropriate order.
[snip]
> There could be a problem with the whole use the new pg_dump to dump 
> the old database.
>
>

Indeed. This kills it.

pg_dump is simply essential as an upgrade mechanism.

The client library approach that has been discussed on and off for years 
seems by far the best approach.


cheers

andrew


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Executor question
Next
From: Andrew Gierth
Date:
Subject: Re: WITH RECUSIVE patches 0723