Re: Refactor pg_dump as a library?

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Jakob Egger <jakob(at)eggerapps(dot)at>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Refactor pg_dump as a library?
Date: 2016-04-14 10:22:30
Message-ID: CAMsr+YEQ+BQO6Q2VHW8R9raubzBMX8SFMhL7FPZZn-q3xJCgDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14 April 2016 at 18:16, Jakob Egger <jakob(at)eggerapps(dot)at> wrote:

> Would anybody else be interested in a pg_dump library?
>

Yes. It comes up a lot, but so far nobody's had the time and energy to
actually do the required refactoring.

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)
>

I'd find a pg_get_tabledef(...) built-in function more interesting for this
particular purpose than pg_dump as a library would be. We already have
pg_get_viewdef(...), pg_get_functiondef(...) etc.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bert 2016-04-14 10:35:03 Re: Problems with huge_pages and IBM Power8
Previous Message Jakob Egger 2016-04-14 10:16:19 Refactor pg_dump as a library?