Yes, IMHO this looks like a god idea. I planed to do something like that,
but to return some kind of description language (XML for example),so restore
could decide at runtime what exactly to do with that metadata ( depending on
what user wants - create database or not, create users or not, reset
serializators or not, replace existing objects or just create objects that
are not existing at database, even do a "pgpatch" on existing objects), but
this needs more time than I currently have :-(
I still hope I'll do it some day...
Regards !
----- Original Message -----
From: "Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
To: "Mark Gibson" <gibsonm@cromwell.co.uk>
Cc: "Hackers (PostgreSQL)" <pgsql-hackers@postgresql.org>
Sent: Tuesday, September 14, 2004 10:44 AM
Subject: Re: [HACKERS] pg_dump as a bunch of PostgreSQL functions
> > Would this be practical, would it be possible to break the pg_dump
> > code out into PostgreSQL functions?
> >
> > Anyone have any ideas/thoughts/suggestions on this?
>
> It's been my plan for sometime, I'm time-starved at the moment however.
>
> Chris
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>
