Re: PL/pgSQL: SELECT INTO EXACT - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: PL/pgSQL: SELECT INTO EXACT
Date
Msg-id 200508130153.j7D1rPL20132@candle.pha.pa.us
Whole thread Raw
In response to Re: PL/pgSQL: SELECT INTO EXACT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PL/pgSQL: SELECT INTO EXACT  (Matt Miller <mattm@epx.com>)
List pgsql-patches
This has been saved for the 8.2 release:

    http://momjian.postgresql.org/cgi-bin/pgpatches_hold

---------------------------------------------------------------------------

Tom Lane wrote:
> Matt Miller <mattm@epx.com> writes:
> >>> I can attach a patch that supports [EXACT | NOEXACT].
> >>
> >> Somehow, proposing two new reserved words instead of one doesn't seem
> >> very responsive to my gripe :-(.
>
> > My intention was to introduce the idea that the current behavior should
> > be changed, and to then suggest a path that eventually eliminates all
> > the new reserved words.
>
> Once you put 'em in, you can't ever really get rid of 'em :-( ... so I'd
> prefer to investigate a path that doesn't use that syntax in the first
> place.
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] For review: Server instrumentation patch
Next
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #1794: inheritance removes permissions from