From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Christopher Browne <cbbrowne(at)gmail(dot)com>, Samuel PHAN <samuel(at)nomao(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Add SPI results constants available for PL/* |
Date: | 2012-01-04 02:11:17 |
Message-ID: | 4F03B545.7070805@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 01/03/2012 08:40 PM, Robert Haas wrote:
> On Tue, Jan 3, 2012 at 9:33 AM, Pavel Stehule<pavel(dot)stehule(at)gmail(dot)com> wrote:
>>> I'd suppose it interesting to add a table to pg_catalog containing this data.
>> - it is useless overhead
> I tend to agree.
>
>> I am expecting so definition some constants in Perl, Python is simple
> Presumably one could instead write a script to transform the list of
> constants into a .pm file that could be loaded into the background, or
> whatever PL/python's equivalent of that concept is. Not sure if
> there's a better way to do it.
Yeah, I'm with you and Pavel. Here's my quick perl one-liner to produce
a set of SPI_* constants for pl/perl. I'm looking at the best way to
include this in the bootstrap code.
perl -ne 'BEGIN { print "use constant\n{\n"; } END { print "};\n"; }
print "\t$1 => $2,\n" if /#define (SPI_\S+)\s+\(?(-?\d+)\)?/;'
src/include/executor/spi.h
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2012-01-04 02:13:57 | Re: ordering op for WHERE |
Previous Message | Robert Haas | 2012-01-04 02:02:22 | Re: controlling the location of server-side SSL files |