X-Original-To: pgsql-admin@postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by developer.postgresql.org (Postfix) with ESMTP id 57112925075 for ; Fri, 23 May 2003 14:00:34 -0400 (EDT) Received: from developer.postgresql.org ([64.117.224.193]) by localhost (developer.postgresql.org [64.117.224.193:10024]) (amavisd-new) with ESMTP id 42375-05 for ; Fri, 23 May 2003 14:00:21 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by developer.postgresql.org (Postfix) with ESMTP id DD7109250B6 for ; Fri, 23 May 2003 13:49:33 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h4NHnXU6017269; Fri, 23 May 2003 13:49:33 -0400 (EDT) To: "David F. Skoll" Cc: pgsql-admin@postgresql.org Subject: Re: upgrade issue In-reply-to: References: <3ECE29A4.2010107@virginia.edu> <3ECE42A1.8040805@virginia.edu> Comments: In-reply-to "David F. Skoll" message dated "Fri, 23 May 2003 12:23:22 -0400" Date: Fri, 23 May 2003 13:49:33 -0400 Message-ID: <17268.1053712173@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new X-Archive-Number: 200305/341 X-Sequence-Number: 8903 "David F. Skoll" 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