Re: 8.1 release notes

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: 8.1 release notes
Date: 2005-08-24 12:04:01
Message-ID: 200508240804.01250.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wednesday 24 August 2005 02:01, Jim C. Nasby wrote:
> On Wed, Aug 24, 2005 at 12:26:21AM -0400, Tom Lane wrote:
> > "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.
>
> The 'autocommit fiasco' isn't ringing a bell right now, so I'll take
> your word for it. :)
>
> Bruce, can you add some info about this to
> http://candle.pha.pa.us/cgi-bin/pgescape ? I intend to link to that when
> I submit a patch to the release notes that links to more info on the
> individual items.

it seems odd to me to be linking to random pages on the net from the release
notes... could that content be folder into the docs themselves and then a
pointer to the relevent section of the docs be given instead?

--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2005-08-24 12:10:13 Re: PATCH to allow concurrent VACUUMs to not lock each
Previous Message Teodor Sigaev 2005-08-24 11:52:27 Re: VACUUM/t_ctid bug (was Re: GiST concurrency commited)