| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: searching in array function - array_position |
| Date: | 2015-03-10 19:45:15 |
| Message-ID: | CA+TgmoZisDDta5sKNRNLP-yAtOvq926g9Frqd=JVtzwAKYvWqA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 10, 2015 at 3:43 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> I have not good feeling about it too. If we would to enhance this are, we
> probably need a specific flinfo field and flags to specify more precious the
> context of cached informations. my_extra should be reserved for generic
> usage. But still there is relative big space for settings some less common
> fields like "proc".
>
> With extra field in flinfo we can have interface like
>
> bool set_flinfo_type_cache(fcinfo, type, flags);
> and usage fcinfo->flinfo->typecache->typlen, ..
>
> I agree with Robert, this can be nice, but it needs more time for design :(
OK. If I'm in the minority, I'll desist.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-03-10 20:03:15 | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |
| Previous Message | Pavel Stehule | 2015-03-10 19:43:09 | Re: proposal: searching in array function - array_position |