From: Tom Lane <tgl@sss.pgh.pa.us>
To: David F. Skoll <dfs@roaringpenguin.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: upgrade issue
Date: Fri, 23 May 2003 13:49:33 -0400
Message-ID: <17268.1053712173@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.55.0305231222140.2907@shishi.roaringpenguin.com>
References: <3ECE29A4.2010107@virginia.edu>
<Pine.GSO.4.55.0305231907220.28360@ra.sai.msu.su>
<3ECE42A1.8040805@virginia.edu>
<Pine.LNX.4.55.0305231222140.2907@shishi.roaringpenguin.com>
"David F. Skoll" <dfs@roaringpenguin.com> writes:
> I have a customer who symlinked libpg.so.3 to libpg.so.2 and he hasn't
> reported problems.
> I don't really advocate this, but at the same time, it's a quick fix :-)
The binary-level incompatibility only affects clients that use NOTIFY,
so for most applications you should be able to get away with the above.
The real solution of course is not to remove libpg.so.2 when you
upgrade, if you are not upgrading everything that uses it.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, dfs@roaringpenguin.com
Subject: Re: upgrade issue
In-Reply-To: <17268.1053712173@sss.pgh.pa.us>
References: <3ECE29A4.2010107@virginia.edu> <Pine.GSO.4.55.0305231907220.28360@ra.sai.msu.su> <3ECE42A1.8040805@virginia.edu> <Pine.LNX.4.55.0305231222140.2907@shishi.roaringpenguin.com> <17268.1053712173@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox