AW: AW: AW: Modified pg_dump & new pg_restore need test ing... - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: AW: AW: Modified pg_dump & new pg_restore need test ing...
Date
Msg-id 219F68D65015D011A8E000006F8590C605BA59B3@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List pgsql-hackers
Philip Warner [mailto:pjw@rhyme.com.au] wrote:
> At 10:39 3/07/00 +0200, Zeugswetter Andreas SB wrote:
> >
> >Could the text format be changed in a compatible way, 
> >that would allow pg_restore's features ? I am thinking of 
> inserted comment 
> >lines that describe the needed sections. 
> 
> Quite possibly; although part of my motivation in writing to 
> the new format
> was to avoid writing a text parser. 

Yes, you are probably right.

> There is no reason why it couldn't use
> a text file by doing a pass through the file to construct a 
> TOC, but this
> seems like a bad idea for large backups, and not really 
> necessary for small
> backups (especially with the -Z option).
> 
> That said, I'm happy to give it a go - the output file is 
> already pretty
> 'parsable'.

I guess it is probably really not worth the trouble.

> 
> 
> >Imho the new default format does not need to be compatible 
> >with pg_dump's output. I would still not compress by default.
> 
> I'm happy to do this; at the moment it uses zlib default 
> compression by

Do we already check for zlib ? It is probably not available everywhere.

Andreas


pgsql-hackers by date:

Previous
From: Zeugswetter Andreas SB
Date:
Subject: AW: AW: Modified pg_dump & new pg_restore need testing. ..
Next
From: "Grigori Soloviov"
Date:
Subject: Fw: PLPGSQL - does not support more than 8 args?