Re: 64-bit API for large object

Tatsuo Ishii <ishii@postgresql.org>

From: Tatsuo Ishii <ishii@postgresql.org>
To: amit.kapila@huawei.com
Cc: kaigai@kaigai.gr.jp, anzai@sraoss.co.jp, pgsql-hackers@postgresql.org
Date: 2012-10-07T07:54:56Z
Lists: pgsql-hackers

Attachments

Amit,

> Today when I tried to build the latest code on my windows m/c, I got few errors from the checkin of this patch.
> 
> lo_hton64 (due to -- unint32_t)
>  .\src\interfaces\libpq\fe-lobj.c(1049) : error C2065: 'uint32_t' : undeclared identifier
> inv_seek (due to   -- MAX_LARGE_OBJECT_SIZE)
> \src\backend\storage\large_object\inv_api.c(389) : error C2065: 'LOBLKSIZELL' : undeclared identifier
> inv_read ((due to   -- MAX_LARGE_OBJECT_SIZE))
> \src\backend\storage\large_object\inv_api.c(441) : error C2065: 'LOBLKSIZELL' : undeclared identifier

Thanks for the report. Can you please try included patch?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Remove all the special-case code for INT64_IS_BUSTED, per decision that