| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Alexandr <askellio(at)gmail(dot)com>, "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 16:14:11 |
| Message-ID: | 20140321161410.GT6899@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MauMau | 2014-03-21 16:17:09 | Re: [bug fix] pg_ctl always uses the same event source |
| Previous Message | Simon Riggs | 2014-03-21 16:11:12 | Re: ALTER TABLE lock strength reduction patch is unsafe Reply-To: |