Tom Lane wrote: > "Merlin Moncure" <[EMAIL PROTECTED]> writes: >> I also agree with Andrew that pgfoundry is not a appropriate place for >> userlocks. They should be properly documented with a cleaned up api. >> I have no objection from them being removed from contrib in the short >> term due to the gpl issue, although I am not sure how you can >> copyright a function wrapper. > > Right, I see the pgfoundry project as just a backwards-compatibility > thing for anyone who doesn't want to change their code. I'm happy to > put some cleaned-up functions into core right now (ie, for 8.2) if > someone will do the legwork to define and implement them.
hmm - that is all a nice and such - but is it really a good idea to do this that late in the release-cycle ? I think the most "natural" thing would be to replace the existing GPL'd userlock code with the new one and discuss the API-change one for 8.3 and up ... Stefan ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings
