RE: current is broken - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject RE: current is broken
Date
Msg-id 20000913213528F.t-ishii@sra.co.jp
Whole thread Raw
In response to RE: current is broken  (Philip Warner <pjw@rhyme.com.au>)
Responses RE: current is broken
List pgsql-hackers
> >BTW, does anybody know about the status of pg_dump? It seems tons of
> >features have been added, but I wonder if all of them are going to
> >appear in 7.1.  Especially now it seems to have an ability to dump
> >Blobs, but the flag (-b) to enable the feature has been disabled. Why?
> 
> Is it? AFAIK, it should not have been disabled. The long params version is
> --blob - does that work?

Ok, long params works. It seems just adding 'b' to the third argument
of getopt() solves "-b" option problem. Do you wnat to fix by yourself?

> Personally, I'd like to see them in 7.1, unless the testing period
> reveals a swag of major flaws...  Once CVS is up again, I intend to
> do a little more work on pg_dump, so now would be a good time to let
> me know if there are problems.

New pg_dump looks great. Could you add docs for it so that we can test
it out?
--
Tatsuo Ishii


pgsql-hackers by date:

Previous
From: Philip Warner
Date:
Subject: RE: current is broken
Next
From: Philip Warner
Date:
Subject: RE: current is broken