Re: pg_dumpall and version confusion

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dumpall and version confusion
Date: 2007-03-15 23:51:18
Message-ID: 45F9DBF6.10304@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Dave Page wrote:
> Tom Lane wrote:
>> I have *no* interest in trying to get it to support an --output-version
>> switch...
>
> There speaks a man who has the luxury of not having to worry about
> multi-version admin tools :-(

I am afraid that I have to agree with Tom here. Pg_dump has plenty of
other deficiencies let's not add to complexity by having an
--output-version.

If you want that, create a wrapper program that calls to different
statically compiled versions of pg_dump.

Joshua D. Drake

>
> /D
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org/
>

--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Stefan Berglund 2007-03-15 23:54:53 Re: Is This A Set Based Solution?
Previous Message Jasbinder Singh Bali 2007-03-15 23:51:03 exception handling in plperlu