Re: QSoC proposal: Rewrite pg_dump and pg_restore

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alexandr <askellio(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: QSoC proposal: Rewrite pg_dump and pg_restore
Date: 2014-03-21 01:28:13
Message-ID: CA+TgmoYHkincYm29JRREcMLXbj9y+Erob5wB+EmBCAzn7Qkymg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Mar 18, 2014 at 8:41 PM, Alexandr <askellio(at)gmail(dot)com> wrote:
> Rewrite (add) pg_dump and pg_restore utilities as libraries (.so, .dll &
> .dylib)

This strikes me as (1) pretty vague and (2) probably too hard for a
summer project.

I mean, getting the existing binaries to build libraries that you can
call with some trivial interface that mimics the existing command-line
functionality of pg_dump might be doable, but that's not all that
interesting. What people are really going to want is a library with a
sophisticated API that lets you do interesting things
programmatically. But that's going to be hard. AFAIK, nobody's even
tried to figure out what that API should look like. Even if we had
that worked out, a non-trivial task, the pg_dump source code is a
mess, so refactoring it to provide such an API is likely to be a job
and a half.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2014-03-21 01:56:15 Re:
Previous Message Behn, Edward (EBEHN) 2014-03-20 21:54:17 Array of composite types returned from python