| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 8.1 release notes |
| Date: | 2005-08-24 04:26:21 |
| Message-ID: | 21129.1124857581@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jim C. Nasby" <jnasby(at)pervasive(dot)com> writes:
> Is the intention that standard_conforming_strings will always be
> read-only?
For the moment it's read-only false; the long-term goal is that it will
be read-only true. In between we will have a release or three where it
is modifiable to some extent. I personally think it would be a *bad*
idea if it were a mere USERSET variable --- we learned from the
autocommit fiasco that changing fundamental semantics on a whim does
not work. But there will need to be some way to alter it for testing
purposes during the interregnum.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-24 04:49:15 | Re: SHOW, RESET require quotes, SET doesn't |
| Previous Message | Stephan Szabo | 2005-08-24 03:47:55 | Work-in-progress referential action trigger timing patch |