-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
Robert Haas wrote: > But I'm neither willing to commit a patch to fix the day before rc1 > nor to argue that the whole release cycle should be put back by > several weeks on account of this issue. Seriously? First, not sure why this would put the whole release cycle back by 'several weeks'. Second, this is removing functionality, so what are apps supposed to do - have a three-choice case in the code to handle pg_am for < 9.6, do some ugly parsing for 9.6, and use the new functions when 10.0 comes out?! This issue was raised on July 25th, and the OP has gone out of his way to present the case and provide patches. It's hardly fair to discard it now. - -- Greg Sabino Mullane g...@turnstep.com End Point Corporation http://www.endpoint.com/ PGP Key: 0x14964AC8 201608071606 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAlenlWUACgkQvJuQZxSWSsjjeACfVrThYGx+4DnBwO2ZAOYGoK7s wdgAoOoxdVo0RM7smSr3CJg8J4dM3YMo =+m9i -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
