| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | kaigai(at)kaigai(dot)gr(dot)jp, ishii(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org, anzai(at)sraoss(dot)co(dot)jp, nagata(at)sraoss(dot)co(dot)jp |
| Subject: | Re: 64-bit API for large object |
| Date: | 2012-09-21 15:24:40 |
| Message-ID: | 20120922.002440.290918912754587128.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> writes:
>> My preference is nothing are changed both pg_getmsgint64() of the backend
>> and routines under PQfn() of the libpq. Isn't it unavailable to deliver int64-
>> value "after" the endian translation on the caller side?
>
> Right. If we had to change anything on the backend side, it would mean
> we had a wire protocol change, which is even less acceptable than a
> libpq ABI change.
The patch does not touch pg_getmsgint64() and I don't think we are not
going have a wire protocol change.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kohei KaiGai | 2012-09-21 15:46:23 | Re: 64-bit API for large object |
| Previous Message | md@rpzdesign.com | 2012-09-21 14:58:48 | DB & Schema |