On Tue, Jun 12, 2012 at 9:52 PM, Tom Lane <[email protected]> wrote: > The code for this is as attached. Note that I'd rip out the normal-path > tracking of line boundaries; it seems better to have a second scan of > the data in the error case and save the cycles in non-error cases.
Really?! -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
