| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump.c |
| Date: | 2011-09-11 15:26:59 |
| Message-ID: | CA+TgmoY=eFj+Z+MjG95YEm3t=zksXN7BtEbnAk4AXpTr=Fs7yQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 8, 2011 at 3:20 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> In the "refactoring Large C files" discussion one of the biggest files Bruce
> mentioned is pg_dump.c. There has been discussion in the past of turning
> lots of the knowledge currently embedded in this file into a library, which
> would make it available to other clients (e.g. psql). I'm not sure what a
> reasonable API for that would look like, though. Does anyone have any ideas?
A good start might be to merge together more of pg_dump and pg_dumpall
than is presently the case.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-09-11 16:18:40 | Re: pg_dump.c |
| Previous Message | David Fetter | 2011-09-11 14:25:07 | Re: pg_dump.c |