Re: Representing a SRF return column in catalogs

From: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Representing a SRF return column in catalogs
Date: 2014-11-07 22:25:49
Message-ID: CAOeZVictOjuvm4+x6takef5bbuGFZUWX_Kdo5HV1AWVSiT540Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Saturday, November 8, 2014, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

>
> I'm confused too. The original example seemed to imagine that details
> of a query (not the function, but the calling query) would be stored in
> the catalogs, which is completely nuts.
>
> pg_proc already has provisions to remember the names of output parameters
> of a function, but it seems like you want something else than that, only
> it's not very clear what. Are you trying to say that you'd like to
> represent the sort order of the output of a function? If so, you'd have
> to add new columns to pg_proc for that, but I can't see why we'd represent
> that information in terms of column names. A column number and a sort
> operator would make more sense.
>
>
Exactly. I would like to represent the sort order of the output.

Thanks for catching it, I really need to stop writing emails without
drinking coffee...

--
Regards,

Atri
*l'apprenant*

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-11-07 22:46:46 Re: [v9.5] Custom Plan API
Previous Message Josh Berkus 2014-11-07 22:03:35 Re: recovery_target_time and standby_mode