Message-ID: <460152B1.8040101@cox.net>
Date: Wed, 21 Mar 2007 10:43:45 -0500
From: Ron Johnson <ron.l.johnson@cox.net>
User-Agent: Icedove 1.5.0.10 (X11/20070307)
MIME-Version: 1.0
To: pgsql-general@postgresql.org
Subject: Re: Anyone still using the sql_inheritance parameter?
References: <28097.1174488581@sss.pgh.pa.us>
In-Reply-To: <28097.1174488581@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/21/07 09:49, Tom Lane wrote:
> Is anybody still using the ability to set sql_inheritance to OFF?
> I'm considering removing the parameter in PG 8.3, so that the current
> default behavior (sql_inheritance = ON) would be the only behavior.
> sql_inheritance was created in 7.1 to allow existing applications to
> not be broken when we changed the default behavior, but I have not
> heard of anyone using it recently.
> 
[snip]
> 
> So: would anyone cry if sql_inheritance disappeared in 8.3?
> 
> If there are a lot of complaints, a possible compromise is to keep the
> variable but make it SUSET, ie, only changeable by superusers.  This
> would still allow the setting to be turned off for use by legacy
> applications (probably by means of ALTER USER) while removing the
> objection that non-privileged users could break things.

Shouldn't features be deprecated for a version before removal?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGAVKxS9HxQb37XmcRAmTbAKDfcRX1zP5NWqVjiiAb/p5KL8vdPACePdip
HCIWBGMMbZVkUuO92h+fOos=
=sVjt
-----END PGP SIGNATURE-----