Magnus Hagander wrote:
I don't think any of us realized the change would affect
third-party projects.
To help specifically PL/Java next time, is there any chance to get it
included in the buildfarm builds? If it had been there, it would've been
caught right away...
Currently buildf
> > This change will force me to a) introduce patch level sensitive
> > conditionals in the code, and b) have two PostgreSQL 8.1.n
> compatible
> > releases of PL/Java. One where n < 4 and another where n >=
> 4. I would
> > like to avoid this in the future if possible. API's should remain
>
Thomas Hallgren wrote:
> The world is not perfect and I know that you are normally very
> restrictive in what is back-patched from head into bug-fix branches. The
> 8.1.4 release however, did introduce a problem. You changed the API
> function inv_open() with the comment "Revise large-object acc
The world is not perfect and I know that you are normally very
restrictive in what is back-patched from head into bug-fix branches. The
8.1.4 release however, did introduce a problem. You changed the API
function inv_open() with the comment "Revise large-object access
routines to avoid running
