Re: Re: COPY BINARY file format proposal

At 15:36 6/12/00 -0500, Tom Lane wrote:
>Grumble, I forgot about COPY WITH OIDS. Amend that proposal as follows:
>
>... We should use two different
>magic numbers depending on whether OIDs are included in the dump or not.

I'd prefer to see a single magic number for all binary COPY output, then a
few bytes of header including a version number, and flags to indicate
endianness, OIDs etc. It seems a lot cleaner than overloading the magic
number.

Also, IIRC part of the problem with text-based COPY is that we can't
specify field order (I think this affectes dumping the regression DB).
Would it be possible to add the ability to (a) specify field order, and (b)
dump a subset of fields?

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/