Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: RFD: Don't force plpgsql IN parameters to constant
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Steve Prentice <prentice(at)cisco(dot)com>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: RFD: Don't force plpgsql IN parameters to constant
- Date: Wed, 29 Jul 2009 23:16:30 -0400
- Message-id: <4206.1248923790@sss.pgh.pa.us> <text/plain>
Steve Prentice <prentice(at)cisco(dot)com> writes: > On Jul 29, 2009, at 4:55 PM, Steve Prentice wrote: >> Tom added a comment in 1995 > For the record, I meant 2005. I was intending to say something like "I've been around this project a long time, but not THAT long" ... regards, tom lane
- Follow-Ups:
- Re: RFD: Don't force plpgsql IN parameters to constant
- From: Alvaro Herrera
- Re: RFD: Don't force plpgsql IN parameters to constant
- References:
- RFD: Don't force plpgsql IN parameters to constant
- From: Steve Prentice
- Re: RFD: Don't force plpgsql IN parameters to constant
- From: Steve Prentice
- RFD: Don't force plpgsql IN parameters to constant
- Prev by Date: machine-readable explain output v4
- Next by Date: Re: question about the _SPI_save_plan() and plan cache
- Previous by thread: Re: RFD: Don't force plpgsql IN parameters to constant
- Next by thread: Re: RFD: Don't force plpgsql IN parameters to constant
- Indexes: