Re: Not quite a security hole in internal_in

Поиск
Список
Период
Сортировка
От Greg Sabino Mullane
Тема Re: Not quite a security hole in internal_in
Дата
Msg-id 020f1528355ca84120fdc99e8efce168@biglumber.com
обсуждение исходный текст
Ответ на Not quite a security hole in internal_in  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Not quite a security hole in internal_in  (Robert Haas <robertmhaas@gmail.com>)
Re: Not quite a security hole in internal_in  (Tom Lane <tgl@sss.pgh.pa.us>)
Список 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@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200906091241
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

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




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Joe Conway
Дата:
Сообщение: Re: [Fwd: Re: dblink patches for comment]
Следующее
От: Jaime Casanova
Дата:
Сообщение: Re: Not quite a security hole in internal_in