Re: API changes in patch release

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Thomas Hallgren <thomas(at)tada(dot)se>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, dallas(dot)morlock(at)gmail(dot)com
Subject: Re: API changes in patch release
Date: 2006-05-23 19:16:09
Message-ID: 200605231916.k4NJG9v18658@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 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.

I don't think any of us realized the change would affect third-party
projects.

--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-05-23 19:18:21 Re: [GENERAL] Weird ..... (a=1 or a=2) <> (a=2 or a=1)
Previous Message Simon Riggs 2006-05-23 19:04:06 Re: Update on sort-compression stuff