| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | kaigai(at)kaigai(dot)gr(dot)jp |
| Cc: | ishii(at)postgresql(dot)org, tgl(at)sss(dot)pgh(dot)pa(dot)us, 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 09:39:28 |
| Message-ID: | 20120921.183928.804379791650069898.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> Hmm, I see. Please deliver the 64bit integer argument as reference,
>>> and don't forget endian translations here.
>>
>> I thought pgPutInt64() takes care of endianness. No?
>>
> It works inside of the PGfn(), when isint = 1 towards pointer data type.
> In my sense, it is a bit problem specific solution.
>
> So, I'd like to see other person's opinion here.
I think we cannot change this because we want to keep the counter part
backend side function pq_getmsgint64() as it is (the function is not
part of the patch).
--
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 09:49:57 | Re: 64-bit API for large object |
| Previous Message | Amit Kapila | 2012-09-21 09:36:06 | Re: ToDo: allow to get a number of processed rows by COPY statement [Review of Patch] |