Re: QSoC proposal: Rewrite pg_dump and pg_restore - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: QSoC proposal: Rewrite pg_dump and pg_restore
Date
Msg-id 20140321161410.GT6899@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: QSoC proposal: Rewrite pg_dump and pg_restore  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan escribió:

> What would be useful for many purposes, and is a long-standing
> project of mine that I still haven't found time to make progress on,
> is that the server should contain functions to produce the creation
> SQL for all its own objects, free of the locks that pg_dump requires
> for consistency.

Maybe you'd like my "DDL deparse" project, then.  Right now it's only of
use for event triggers during DDL execution, but I don't see any strong
reason it cannot be used to reconstruct object creation commands from
only their identifying OID.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: ALTER TABLE lock strength reduction patch is unsafe Reply-To:
Next
From: "MauMau"
Date:
Subject: Re: [bug fix] pg_ctl always uses the same event source