From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Anyone still using the sql_inheritance parameter? |
Date: | 2007-03-21 15:43:45 |
Message-ID: | 460152B1.8040101@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
-----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-----
From | Date | Subject | |
---|---|---|---|
Next Message | brian | 2007-03-21 15:46:45 | Re: select progressive total |
Previous Message | Oleg Bartunov | 2007-03-21 15:42:34 | Re: multi terabyte fulltext searching |
From | Date | Subject | |
---|---|---|---|
Next Message | codeWarrior | 2007-03-21 16:00:25 | Re: Anyone still using the sql_inheritance parameter? |
Previous Message | Joshua D. Drake | 2007-03-21 15:00:21 | Re: Anyone still using the sql_inheritance parameter? |