| From: | Jakob Egger <jakob(at)eggerapps(dot)at> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Refactor pg_dump as a library? |
| Date: | 2016-04-14 10:16:19 |
| Message-ID: | 82EFF560-2A09-4C3D-81CC-A2A5EC438CE5@eggerapps.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Would anybody else be interested in a pg_dump library? I've found a thread from 2013 related to the idea, but the discussion came to nothing.
Thread started here:
http://www.postgresql.org/message-id/71e01949.2e16b.13df4707405.Coremail.shuai900217@126.com
My Motivation:
I'm the developer of a PostgreSQL GUI client, and I am looking for ways to integrate pg_dump into my application. The main use case would be to get the dump of individual tables (for example, when you want to create a table similar to an existing one)
Bundling pg_dump with my application and calling it doesn't allow the fine grained control and integration I would like to have. Also, pg_dump always opens a new connection; I would prefer to use an existing database connection instead.
In case anybody else is interested in this, I can offer to sponsor some developer time towards this effort.
Best regards,
Jakob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-04-14 10:22:30 | Re: Refactor pg_dump as a library? |
| Previous Message | Daniel Verite | 2016-04-14 10:10:45 | Re: \crosstabview fixes |