Re: revised sample SRF C function; proposed SRF API - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: revised sample SRF C function; proposed SRF API
Date
Msg-id GNELIHDDFBOCMGBFGEFOMEKLCCAA.chriskl@familyhealth.com.au
Whole thread Raw
In response to Re: revised sample SRF C function; proposed SRF API  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
> Tom Lane wrote:
> > Well, we're not doing that; and I see no good reason to make the thing
> > be a builtin function at all.  Since it's just an example, it can very
> > well be a contrib item with a creation script.  Probably *should* be,
> > in fact, because dynamically created functions are what other people are
> > going to be building; an example of how to do it as a builtin function
> > isn't as helpful.
>
> True enough, although I could always create another example for contrib.
> Returning GUC variable "SHOW ALL" results as a query result has been
> discussed before, and I thought there was agreement that it was a
> desirable backend feature.

Sure would be.  Means we can show config variables nicely in phpPgAdmin like
phpMyAdmin does...

Chris



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Perl build fix attempted
Next
From: Karel Zak
Date:
Subject: Re: Project scheduling issues (was Re: Per tuple overhead,