Skip site navigation (1) Skip section navigation (2)

RE: COPY BINARY is broken...

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org
Subject: RE: COPY BINARY is broken...
Date: 2000-12-01 22:47:48
Message-ID: 8F4C99C66D04D4118F580090272A7A234D31BE@sectorbase1.sectorbase.com (view raw or flat)
Thread:
Lists: pgsql-hackers
> 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

pgsql-hackers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group