Re: Add SPI results constants available for PL/*

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: 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 01:40:15
Message-ID: CA+TgmoYCpQxwvzy_dkOH081nHcmMcQq==CGvJM50BTsg4snM3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-01-04 01:49:42 Re: 16-bit page checksums for 9.2
Previous Message Robert Haas 2012-01-04 01:37:58 Re: SEGFAULT on SELECT * FROM view