Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [GENERAL] Returning a RECORD, not SETOF RECORD
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Michael Fuhr <mike(at)fuhr(dot)org>
- Cc: Thomas Hallgren <thhal(at)mailblocks(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: [GENERAL] Returning a RECORD, not SETOF RECORD
- Date: Fri, 29 Apr 2005 13:34:49 -0400
- Message-id: <7209(dot)1114796089(at)sss(dot)pgh(dot)pa(dot)us>
Michael Fuhr <mike(at)fuhr(dot)org> writes: > On Fri, Apr 29, 2005 at 10:36:05AM -0400, Tom Lane wrote: >> regression=# select (xyz(unique1,unique2)).* from tenk1 limit 5; > This is a little off topic, but I've noticed that the above invokes > the function once per output column: Yeah, that is unfortunate but doesn't seem very easy to fix. regards, tom lane
- References:
- Re: [GENERAL] Returning a RECORD, not SETOF RECORD
- From: Thomas Hallgren
- Re: [GENERAL] Returning a RECORD, not SETOF RECORD
- From: Tom Lane
- Re: [GENERAL] Returning a RECORD, not SETOF RECORD
- From: Michael Fuhr
- Re: [GENERAL] Returning a RECORD, not SETOF RECORD
- Prev by Date: Re: [GENERAL] Returning a RECORD, not SETOF RECORD
- Next by Date: Re: performance of bitmap scans in nested loop joins
- Previous by thread: Re: [GENERAL] Returning a RECORD, not SETOF RECORD
- Next by thread: PseudoPartitioning and agregates
- Indexes: