From: Christopher Kings-Lynne <chris.kings-lynne@calorieking.com>
To: Jim C. Nasby <jnasby@pervasive.com>
Cc: soni de <soni.de@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Regarding pg_dump utility
Date: Fri, 09 Jun 2006 09:16:35 +0800
Message-ID: <4488CBF3.9040101@calorieking.com> (raw)
In-Reply-To: <20060608151657.GL45331@pervasive.com>
References: <9f2e40a90606072309v4c5b2623k8bda2614cd575835@mail.gmail.com>
<20060608151657.GL45331@pervasive.com>
> 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....
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: chris.kings-lynne@calorieking.com, jnasby@pervasive.com, soni.de@gmail.com
Subject: Re: Regarding pg_dump utility
In-Reply-To: <4488CBF3.9040101@calorieking.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox