Refactor pg_dump as a library? - Mailing list pgsql-hackers

From Jakob Egger
Subject Refactor pg_dump as a library?
Date
Msg-id 82EFF560-2A09-4C3D-81CC-A2A5EC438CE5@eggerapps.at
Whole thread Raw
Responses Re: Refactor pg_dump as a library?
Re: Refactor pg_dump as a library?
List 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
discussioncame 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
mainuse case would be to get the dump of individual tables (for example, when you want to create a table similar to an
existingone) 

Bundling pg_dump with my application and calling it doesn't allow the fine grained control and integration I would like
tohave. 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




pgsql-hackers by date:

Previous
From: "Daniel Verite"
Date:
Subject: Re: \crosstabview fixes
Next
From: Craig Ringer
Date:
Subject: Re: Refactor pg_dump as a library?