| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matt Miller <mattm(at)epx(dot)com> |
| Cc: | pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL: SELECT INTO EXACT |
| Date: | 2005-08-09 00:06:13 |
| Message-ID: | 10611.1123545973@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Matt Miller <mattm(at)epx(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-08-09 00:06:22 | Re: Simplifying wal_sync_method |
| Previous Message | Tom Lane | 2005-08-09 00:04:44 | Re: Simplifying wal_sync_method |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-09 02:21:28 | Re: prevent encoding conversion recursive error |
| Previous Message | Satoshi Nagayasu | 2005-08-08 22:59:39 | Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items) |