From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Davidson, Robert" <robdavid(at)amazon(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: [SQL] Function Parameters in GROUP BY clause cause errors |
Date: | 2006-03-23 04:27:11 |
Message-ID: | 2742.1143088031@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-sql |
I wrote:
> Hmm, this seems like a plpgsql deficiency. It feels it can generate a
> separate parameter symbol ($n) for each occurrence of each variable it
> passes into a SQL query. But for this query to be legal, the two
> instances of IntervalMinutes have to be represented by the *same*
> parameter symbol (notice they are not in the regurgitated query).
> It would be more efficient anyway to not generate multiple parameters
> for the same value, so we oughta fix this.
Patch applied to HEAD and 8.1 branches.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-03-23 04:50:00 | Re: inpricise checkpoint stats |
Previous Message | Christian Paul B. Cosinas | 2006-03-23 01:33:33 | Re: Function Parameters in GROUP BY clause cause errors |
From | Date | Subject | |
---|---|---|---|
Next Message | Davidson, Robert | 2006-03-23 13:30:28 | Re: [SQL] Function Parameters in GROUP BY clause cause errors |
Previous Message | Tom Lane | 2006-03-23 02:47:31 | Re: OUT parameter |