From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | pjw(at)rhyme(dot)com(dot)au |
Cc: | Inoue(at)tpf(dot)co(dot)jp, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgresql(dot)org |
Subject: | RE: current is broken |
Date: | 2000-09-13 12:35:28 |
Message-ID: | 20000913213528F.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2000-09-13 12:41:37 | RE: current is broken |
Previous Message | Denis Perchine | 2000-09-13 11:07:56 | Fwd: Problems inserting data |