Message-ID: <4488CBF3.9040101@calorieking.com>
Date: Fri, 09 Jun 2006 09:16:35 +0800
From: Christopher Kings-Lynne <chris.kings-lynne@calorieking.com>
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: "Jim C. Nasby" <jnasby@pervasive.com>
Cc: soni de <soni.de@gmail.com>, pgsql-performance@postgresql.org
Subject: Re: Regarding pg_dump utility
References: <9f2e40a90606072309v4c5b2623k8bda2614cd575835@mail.gmail.com>
	<20060608151657.GL45331@pervasive.com>
In-Reply-To: <20060608151657.GL45331@pervasive.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> It probably wouldn't be terribly difficult to put the guts of pg_dump
> into a library that you could interface with via C. I'm not sure if the
> community would accept such a patch; though, I seem to recall other
> people asking for this on occasion.
>  
>> I think script support is bit risky because if anything goes wrong while
>> taking backup using pg_dump then user will not understand the problem of
>> falling
>>
>> If only script support is possible then what should we prefer perl or shell?
> 
> Depends on what you're trying to accomplish. Perl is a much more capable
> language than shell, obviously.


In phpPgAdmin we just execute pg_dump as a child process and capture its 
output....