From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Joe Conway" <mail(at)joeconway(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: revised sample SRF C function; proposed SRF API |
Date: | 2002-06-10 06:21:56 |
Message-ID: | GNELIHDDFBOCMGBFGEFOMEKLCCAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak | 2002-06-10 07:35:54 | Re: Project scheduling issues (was Re: Per tuple overhead, |
Previous Message | Tom Lane | 2002-06-10 05:37:03 | Re: Perl build fix attempted |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-06-10 14:18:13 | Re: guc.c and postgresql.conf.sample constistency check |
Previous Message | Joe Conway | 2002-06-10 01:27:39 | contrib/showguc (was Re: [HACKERS] revised sample SRF C function; proposed SRF API) |