Skip site navigation (1) Skip section navigation (2)

Re: unsigned and signed chars in libpq API

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Dmitriy Igrishin <dmitigr(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: unsigned and signed chars in libpq API
Date: 2012-08-27 16:40:37
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Thu, Feb  2, 2012 at 10:33:24AM +0300, Dmitriy Igrishin wrote:
>> Could you tell me please an objective reason why PQunescapeBytea()
>> returns unsigned char* rather than just char* ?
>> I am asking because a bit confused. How this intermixes with LO's API,
>> which based on signed chars (although as we all know large object -
>> is a just bytea splitted on chunks)?
>> And also PQgetvalue() returns char* rather than unsigned char*.

> Can someone answer this?  Are we consistent here?

We're not, particularly, but changing any of this seems likely to
create more pain than it removes.

			regards, tom lane

In response to


pgsql-hackers by date

Next:From: Fujii MasaoDate: 2012-08-27 16:46:18
Subject: Useless removal of duplicate GIN index entries in pg_trgm
Previous:From: Robert HaasDate: 2012-08-27 16:39:02
Subject: Re: Timing overhead and Linux clock sources

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group