Re: pg_dump --split patch - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: pg_dump --split patch
Date
Msg-id m24o9ppwve.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: pg_dump --split patch  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pg_dump --split patch  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> I have to admit I'm a bit unsold on the approach as well.  It seems
> like you could write a short Perl script which would transform a text
> format dump into the proposed format pretty easily, and if you did
> that and published the script, then the next poor shmuck who had the
> same problem could either use the script as-is or hack it up to meet
> some slightly different set of requirements.  Or maybe you'd be better
> off basing such a script on the custom or tar format instead, in order
> to avoid the problem of misidentifying a line beginning with --- as a
> comment when it's really part of a data item.  Or maybe even writing a
> whole "schema diff" tool that would take two custom-format dumps as
> inputs.
>
> On the other hand, I can certainly think of times when even a pretty
> dumb implementation of this would have saved me some time.

You mean like those:
 https://labs.omniti.com/labs/pgtreats/wiki/getddl https://github.com/dimitri/getddl

In this case hacking the perl version was impossible for me to hack on
so my version is in python, but still is somewhat of a fork.  I even
have an intermediate shell version somewhere that a colleague wrote, but
I much prefer maintaining python code.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: back branches vs. VS 2008
Next
From: Dimitri Fontaine
Date:
Subject: Re: Extension upgrade, patch v0: debug help needed