Re: pg_dump(all) library - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump(all) library
Date
Msg-id 23815.1217090808@sss.pgh.pa.us
Whole thread Raw
In response to pg_dump(all) library  (David Fetter <david@fetter.org>)
List pgsql-hackers
David Fetter <david@fetter.org> writes:
> What would a libpgdump API look like?

Hmm.  Start with requirements:

* Ability to enumerate the objects in a database

* Ability to fetch the "properties" of individual objects
(SQL definition is only one property, eg. pg_dump considers
owner, schema, ACL separately from the CREATE command)

* Ability to identify an appropriate dump order (and perhaps
lower-level manipulations of dependency info, not sure what
might be needed)

* Ability to work with different server versions (not sure how
much that impacts the API, but it's definitely something to keep
in mind while designing)

What else?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Kenneth Marshall
Date:
Subject: Re: [RFC] Unsigned integer support.
Next
From: "Joshua D. Drake"
Date:
Subject: Re: pg_dump(all) library