Re: Recompiling Non-PostGres apps when upgrading PostGreSQL - Mailing list pgsql-admin

From Peter Eisentraut
Subject Re: Recompiling Non-PostGres apps when upgrading PostGreSQL
Date
Msg-id Pine.LNX.4.30.0105292321300.757-100000@peter.localdomain
Whole thread Raw
In response to Recompiling Non-PostGres apps when upgrading PostGreSQL  ("Chris Ruprecht" <chrup999@yahoo.com>)
List pgsql-admin
Chris Ruprecht writes:

> In the past, I have rebuilt all my "dependant" binaries, every time I installed a new version of Postgres. "Other
binaries"means php, ssl and apache. However, I'm wondering if I really have to do that if nothing in the API changes. I
know,it might be safe to do it anyway - just in case, but it's quite a bit of time which gets lost, every time I do
that.Any input? 

You don't need to rebuild client applications, unless the shared library
major version changes (because of incompatible changes), in which case you
will be told about it.  (It hasn't happened in recent times.)

Server-side modules might need to be rebuild.

--
Peter Eisentraut   peter_e@gmx.net   http://funkturm.homeip.net/~peter


pgsql-admin by date:

Previous
From: "Chris Ruprecht"
Date:
Subject: Recompiling Non-PostGres apps when upgrading PostGreSQL
Next
From: Tom Lane
Date:
Subject: Re: Re: pqReadData() -- backend closed the channel unexpectedly.