From: | Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com> |
---|---|
To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
Cc: | soni de <soni(dot)de(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Regarding pg_dump utility |
Date: | 2006-06-09 01:16:35 |
Message-ID: | 4488CBF3.9040101@calorieking.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> 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....
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2006-06-09 01:19:15 | Re: Regarding pg_dump utility |
Previous Message | Tom Lane | 2006-06-08 22:19:41 | Re: Why date index is not used |