Re: Not quite a security hole in internal_in

From: "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Not quite a security hole in internal_in
Date: 2009-06-09 16:41:37
Message-ID: 020f1528355ca84120fdc99e8efce168@biglumber.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

> Normally we would consider a pg_proc change as requiring a catversion
> bump. Since we are already past 8.4 beta we couldn't do that without
> forcing an initdb for beta testers.

I think a serious issue like this warrants a bump. It seems like you are
saying that at any other time in the release cycle this would be
an automatic bump, so let's keep a consistent policy and bump it.

- --
Greg Sabino Mullane greg(at)turnstep(dot)com
End Point Corporation
PGP Key: 0x14964AC8 200906091241
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkoukLkACgkQvJuQZxSWSshalACg8UfcyvTF2TxazvwwzxDNDIuM
dpEAoJYVaS8czeR79dyJOTAoXLghSgKS
=21ax
-----END PGP SIGNATURE-----

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-06-09 16:42:52 Re: Multicolumn index corruption on 8.4 beta 2
Previous Message Joe Conway 2009-06-09 16:36:30 Re: [Fwd: Re: dblink patches for comment]