Re: AW: AW: AW: Modified pg_dump & new pg_restore need testing...

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: AW: AW: AW: Modified pg_dump & new pg_restore need testing...
Date: 2000-07-04 05:19:43
Message-ID: 3.0.5.32.20000704151943.0253a870@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 22:39 3/07/00 -0300, The Hermit Hacker wrote:
>
>that will be correct, but its a quick/easy change ... I'll add the code in
>tonight so that its something we check for and set in config.h, so as long
>as you include that, you'll have that setting available ...
>

OK. Heres a patch against CVS (pre new pg_dump). This is a complete patch,
so you can throw away the last two...

Bye for now,

Philip

Attachment Content-Type Size
pg_dump_cvs_120_patch.gz application/octet-stream 30.0 KB
unknown_filename text/plain 547 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2000-07-04 05:24:37 Re: AW: AW: AW: Modified pg_dump & new pg_restore need testing...
Previous Message Bruce Momjian - CVS 2000-07-04 05:17:04 pgsql/doc/TODO.detail (alpha default distinct flock fsync function limit null pg_shadow primary)