Re: testing plpython3u on 9.0beta2
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>, Peter Eisentraut <peter_e@gmx.net>, Robert Haas <robertmhaas@gmail.com>, Chris <rfusca@gmail.com>, pgsql-hackers@postgresql.org
Date: 2010-06-28T22:59:41Z
Lists: pgsql-hackers
Attachments
- (unnamed) (text/plain)
Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > Josh Berkus wrote: > >>> You could argue it either way. The number of beta testers with > >>> plpython3 installations is probably very small, so I'm kinda leaning to > >>> just changing the code without a catversion bump. OTOH, if we want to > >>> encourage testing of pg_upgrade ... > >> > >> FWIW, the last bump has led to a lot of testing of pgupgrade. > > > And fixes, that will appear in 9.0 beta3. :-) Most fixes were related > > to platform compile portability. > > Well, if you think that pg_upgrade has changed materially since beta2, > that would be a good argument for getting some fresh testing for it, > which in turn argues for doing the catversion bump here. Attached are the changes since beta2; they are pretty minor. The good news is I think all reporters eventually got it working. I assume using it for beta3 would allow it work even better, and once you have use it once, using it again is simple. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. +