When you say pgdump library, do you mean taking all catalog querying
functionality into a contrib like module , exposed as functions and
then have a simple pgdump executable which calls those functions to dump
to a file, because you would still need a pgdump executable i suppose
for people to be able to backup their stuff. Is my understanding
somewhere near actual idea or i am way off here?
Are there any discussions on this topic which could give me a little
more idea? because i would definitely like to take a shot at this.
Andrew Dunstan wrote:
> Usama Munir wrote:
>> I think using pg_dump in some cases is a good option , but not all
>> the time, having a function makes it much cleaner to use
> That's why having a shared pgdump library as has been previously
> mentioned is by far the best solution.
> We have discussed this before, and factoring out this functionality
> into a shared lib is what needs to be done. I'm not convinced it is as
> much work as Tom suggests, but it is certainly a non-trivial task.
In response to
pgsql-hackers by date
|Next:||From: Andrew Dunstan||Date: 2007-05-21 18:27:58|
|Subject: Re: pg_get_tabledef|
|Previous:||From: Karl O. Pinc||Date: 2007-05-21 18:03:41|
|Subject: Re: COPY into a view; help w. design & patch|