> 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
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2006-03-23 04:50:00|
|Subject: Re: inpricise checkpoint stats |
|Previous:||From: Christian Paul B. Cosinas||Date: 2006-03-23 01:33:33|
|Subject: Re: Function Parameters in GROUP BY clause cause errors|
pgsql-sql by date
|Next:||From: Davidson, Robert||Date: 2006-03-23 13:30:28|
|Subject: Re: [SQL] Function Parameters in GROUP BY clause cause errors |
|Previous:||From: Tom Lane||Date: 2006-03-23 02:47:31|
|Subject: Re: OUT parameter |