Re: pgsql: Move strtoint() to common - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Move strtoint() to common
Date
Msg-id 7070.1521153008@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Move strtoint() to common  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: pgsql: Move strtoint() to common
List pgsql-committers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Tom Lane wrote:
>> build now works, ecpg tests fail.

> I stared at the code for a while, didn't notice anything amiss.  I'm
> mystified.  Peter?

I'm wondering if the Windows environment is somehow supplying a
"strtoint" that isn't actually ABI-compatible with ours.

A different theory is that the pg_restrict markers are bollixing things.
No idea how, but they don't look like they're really doing anything for us
optimization-wise, so it doesn't seem unreasonable to remove them and see
if that makes a difference.

            regards, tom lane


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Clean up duplicate table and function names in regressiontests.
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Move strtoint() to common