Re: 7.4 COPY BINARY Format Change

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: 7.4 COPY BINARY Format Change
Дата
Msg-id 24988.1060004641@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: 7.4 COPY BINARY Format Change  (Lee Kindness <lkindness@csl.co.uk>)
Ответы Re: 7.4 COPY BINARY Format Change  (Lee Kindness <lkindness@csl.co.uk>)
Список pgsql-hackers
Lee Kindness <lkindness@csl.co.uk> writes:
> However, is COPY BINARY meant/designed to be used as transfer or
> backup mechanism?

I think you're overlooking a key consideration: COPY BINARY is not
an isolated feature anymore.  By design it uses the same data
representations as are used for binary query parameters and results
in the rest of the 7.4 FE/BE protocol.

I could see some value in providing byte-swapping routines in libpq
to convert between local and network representations for integers and
floats.  The underlying facilities (ntohl etc) are readily available,
of course, but it's a small matter that is easy to get wrong.

I'm not sure it's worth packaging up COPY BINARY logic per se.  I think
you'd end up with an API not materially simpler than dealing with the
format directly.  And I'm unconvinced it'd actually be used widely,
whereas I do expect binary transfer of individual values to be common.
        regards, tom lane


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: DROP TYPE/DROP DOMAIN
Следующее
От: Robert Treat
Дата:
Сообщение: Re: "truncate all"?