-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> Ah, okay, good. I agree with the major version bump. > Does it need updated docs, as well? Yes. > And does this break compatibility at all for those who have > used pg_enable_utf8 in the past? Yes and no. For most cases, those setting pg_enable_utf8 to 0 will still have it behave as it did before - no utf8 flag. Those setting pg_enable_utf8 to 1 explicitly will get mostly the same behavior as before. Those not setting it at all will see the biggest change, as the detection and setting will be automatic. We'll need to spell it all out in the docs and release notes of course. I'll work on a outline of the current thinking and send to the list shortly. - -- Greg Sabino Mullane [email protected] End Point Corporation http://www.endpoint.com/ PGP Key: 0x14964AC8 201101280757 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAk1CvV8ACgkQvJuQZxSWSsj3mQCfX2hUn3xx11mzVIzHBRmrdwNW Tr0AoLw6G06STO1jp5CIdis+je6DnLjo =5a9x -----END PGP SIGNATURE-----
