Re: pgsql: Make the pg_stat_activity view call a SRF

From: "Jaime Casanova" <jcasanov(at)systemguards(dot)com(dot)ec>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Bruce Momjian" <bruce(at)momjian(dot)us>, "Magnus Hagander" <magnus(at)hagander(dot)net>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Make the pg_stat_activity view call a SRF
Date: 2008-08-16 23:46:27
Message-ID: 3073cc9b0808161646j5892f708lbcf40275b1afb628@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Sat, Aug 16, 2008 at 12:03 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> regression=# select * from pg_show_all_settings();
> ERROR: a column definition list is required for functions returning "record"
>
> There's no longer any very good reason for built-in SRFs to not define
> their own output record type.
>

is there any one doing this? if not i want to give it a try... seems
easy enough, even for me :)

--
regards,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. (593) 87171157

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-08-17 01:20:00 pgsql: Improve sublink pullup code to handle ANY/EXISTS sublinks that
Previous Message Bruce Momjian 2008-08-16 19:39:03 pgsql: Update instructions on generating TODO.html.

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-08-17 01:35:06 Re: Limitations on trigger functions
Previous Message Dan Eloff 2008-08-16 23:35:01 Limitations on trigger functions