API changes in patch release - Mailing list pgsql-hackers

From Thomas Hallgren
Subject API changes in patch release
Date
Msg-id 4472B3C8.2090608@tada.se
Whole thread Raw
Responses Re: API changes in patch release
List pgsql-hackers
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 with CurrentMemoryContext".

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 stable 
during patch releases.

Having said that, I've been in the game long enough to know that Utopia 
doesn't exist. You probably had a very good reason to break the 
compatibility.

Kind Regards,
Thomas Hallgren



pgsql-hackers by date:

Previous
From: Jeff Frost
Date:
Subject: Re: [ADMIN] does wal archiving block the current client connection?
Next
From: Thomas Hallgren
Date:
Subject: Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?)