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: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: Steve Prentice <prentice(at)cisco(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: RFD: Don't force plpgsql IN parameters to constant
- Date: Thu, 30 Jul 2009 19:59:23 -0400
- Message-id: <20090730235923.GI6459@alvh.no-ip.org> <text/plain>
Tom Lane wrote: > 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" ... I was looking at a 1997 pgsql-hackers mailbox yesterday and I noticed that "tgl" back then was Thomas Lockhart. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
- 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
- Re: RFD: Don't force plpgsql IN parameters to constant
- From: Tom Lane
- RFD: Don't force plpgsql IN parameters to constant
- Prev by Date: Re: bytea vs. pg_dump
- Next by Date: Re: PATCH: make plpgsql IN args mutable (v1)
- Previous by thread: Re: RFD: Don't force plpgsql IN parameters to constant
- Next by thread: machine-readable explain output v4
- Indexes: