| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump(all) library |
| Date: | 2008-07-26 17:44:16 |
| Message-ID: | 488B6270.9040408@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-07-26 17:56:14 | Re: pg_dump additional options for performance |
| Previous Message | Tom Lane | 2008-07-26 17:43:06 | Re: pg_dump additional options for performance |