| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Chris Ruprecht <chrup999(at)yahoo(dot)com> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Recompiling Non-PostGres apps when upgrading PostGreSQL |
| Date: | 2001-05-29 21:23:51 |
| Message-ID: | Pine.LNX.4.30.0105292321300.757-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmx(dot)net http://funkturm.homeip.net/~peter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-05-29 22:28:53 | Re: Re: pqReadData() -- backend closed the channel unexpectedly. |
| Previous Message | Chris Ruprecht | 2001-05-29 20:37:15 | Recompiling Non-PostGres apps when upgrading PostGreSQL |