Re: [BUGS] \copy produces CSV output that cannot be read by \copy

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [BUGS] \copy produces CSV output that cannot be read by \copy
Дата
Msg-id 1473.1501951948@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [BUGS] \copy produces CSV output that cannot be read by \copy  (Michael Paquier <michael.paquier@gmail.com>)
Ответы Re: [BUGS] \copy produces CSV output that cannot be read by \copy
Список pgsql-bugs
Michael Paquier <michael.paquier@gmail.com> writes:
> The format produced by COPY OUT looks fine to me, and can be reloaded
> with a plain COPY (not \copy). And you may be interested in this bit
> from src/bin/psql/copy.c:
>                     /*
>                      * This code erroneously assumes '\.' on a line alone
>                      * inside a quoted CSV string terminates the \copy.
>                      *
> http://www.postgresql.org/message-id/E1TdNVQ-0001ju-GO@wrigleys.postgresql.org
>                      */

I wonder if it would improve matters to check for "\." only when
copystream == pset.cur_cmd_source, that is, only when the copy data
is inlined into the SQL stream.  That would create an inconsistency
between inline and out-of-line data, but it might be a reasonable
thing to do anyway.
        regards, tom lane


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [BUGS] \copy produces CSV output that cannot be read by \copy
Следующее
От: Andres Freund
Дата:
Сообщение: Re: [BUGS] [BUG] pg9.4.10 Logical decoding did not get the correctoldtuplelen