> 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
- Re: [HACKERS] COPY BINARY is broken... Alfred Perlstein
- Re: [HACKERS] COPY BINARY is broken... Tom Lane
- Re: [HACKERS] COPY BINARY is broken... Alfred Perlstein
- Re: [HACKERS] COPY BINARY is broken... Don Baccus
- Re: [HACKERS] COPY BINARY is broken... Samuel Sieb
- Re: [HACKERS] COPY BINARY is broken... Bruce Momjian
- Re: [HACKERS] COPY BINARY is broken... Bruce Momjian
- RE: [HACKERS] COPY BINARY is broken... Mikheev, Vadim
- Re: [HACKERS] COPY BINARY is broken... Mikheev, Vadim
- Re: [HACKERS] COPY BINARY is broken... Adriaan Joubert