Re: pgsql: plpython: Add SPI cursor support

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Urbański <wulczer(at)wulczer(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-committers(at)postgresql(dot)org, Steve Singer <ssinger(at)ca(dot)afilias(dot)info>
Subject: Re: pgsql: plpython: Add SPI cursor support
Date: 2012-01-10 14:28:58
Message-ID: 4F0C4B2A.7050601@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 01/10/2012 04:56 AM, Dave Page wrote:
> On Mon, Jan 9, 2012 at 5:32 PM, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>>
>> On 01/09/2012 12:13 PM, Peter Geoghegan wrote:
>>> On 9 January 2012 17:06, Dave Page<dpage(at)pgadmin(dot)org> wrote:
>>>> Is there a way I can get gcc to spit out the expanded definition in a
>>>> readable format that you know of?
>>> Yes. Figure out what flags gcc is given when building the TU. Then,
>>> add the -E flag and see what is generated:
>>>
>>> http://www.network-theory.co.uk/docs/gccintro/gccintro_36.html
>>
>>
>> Yeah, something like
>>
>> gcc -E -I/usr/include/python2.7/ -include Python.h
>> /usr/include/python2.7/object.h
>>
>> adjusted for your paths should do it.
> Thanks - pfa.

which contains:

__attribute__((dllimport)) PyObject * PyObject_SelfIter(PyObject *);

The result is identical on frogmouth, which builds happily using gcc
4.5.0. So this does look like a compiler quirk.

cheers

andrew

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Dave Page 2012-01-10 14:30:37 Re: pgsql: plpython: Add SPI cursor support
Previous Message Dave Page 2012-01-10 09:56:30 Re: pgsql: plpython: Add SPI cursor support

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2012-01-10 14:30:37 Re: pgsql: plpython: Add SPI cursor support
Previous Message Merlin Moncure 2012-01-10 14:10:01 Re: LWLOCK_STATS