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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: [BUGS] BUG #2114: (patch) COPY FROM ... end of copy

  • From: Andrew Dunstan <andrew(at)dunslane(dot)net>
  • To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
  • Cc: Ben Gould <ben(dot)gould(at)free(dot)fr>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
  • Subject: Re: [BUGS] BUG #2114: (patch) COPY FROM ... end of copy
  • Date: Tue, 27 Dec 2005 09:51:08 -0500
  • Message-id: <43B154DC.8090100@dunslane.net> <text/plain>


Bruce Momjian wrote:


The big problem is that \. is also a valid
CSV data value (though not a valid non-CSV data value).  So, the
solution we came up with was to require \. to appear alone on a line in
CSV mode for it to be treated as end-of-copy.
According to the docs, that's the way to specify EOD in both text and CSV mode:
End of data can be represented by a single line containing just backslash-period. 

Your analysis regarding line_buf.len seems correct.

We probably should have a regression test with \. in a CSV field.

cheers

andrew
Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group