> The existing COPY BINARY file format is entirely brain-dead 
> anyway; for example, it wants the number of tuples to be stored
> at the front, which means we have to scan the whole relation an
> extra time to get that info. Its handling of nulls is bizarre, too.
> I'm thinking this might be a good time to abandon backwards
> compatibility and switch to a format that's a little easier to read
> and write.  Does anyone have an opinion pro or con about that?

Switch to new format.

Vadim

Responses

• Re: COPY BINARY is broken... at 2000-12-03 16:44:29 from Adriaan Joubert

pgsql-hackers by date

Next:	From: Mikheev, Vadim	Date: 2000-12-01 22:50:07
	Subject: RE: COPY BINARY is broken...
Previous:	From: Tom Lane	Date: 2000-12-01 22:35:33
	Subject: COPY BINARY is broken...