Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dzrHt-0000XC-Sb for pgsql-admin@arkaria.postgresql.org; Wed, 04 Oct 2017 21:33:05 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dzrHs-0007M2-V9 for pgsql-admin@arkaria.postgresql.org; Wed, 04 Oct 2017 21:33:05 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dzrHs-0007Ls-CZ for pgsql-admin@postgresql.org; Wed, 04 Oct 2017 21:33:04 +0000 Received: from ns5.gunduz.org ([107.170.136.15] helo=ns1.gunduz.org) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dzrHo-00064w-Uf for pgsql-admin@postgresql.org; Wed, 04 Oct 2017 21:33:02 +0000 Received: from asus-laptop03.gunduz.org (unknown [88.98.219.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ns1.gunduz.org (Postfix) with ESMTPSA id 7BE783FCF9; Wed, 4 Oct 2017 21:32:57 +0000 (UTC) Message-ID: <1507152775.3791.53.camel@gunduz.org> Subject: Re: psql can't connect to old DB after installing new binaries From: Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= To: Don Seiler , Tom Lane Cc: pgsql-admin Date: Wed, 04 Oct 2017 22:32:55 +0100 In-Reply-To: References: <21116.1507147420@sss.pgh.pa.us> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-8QZK5FZUUtfuIsC3ovfP" X-Mailer: Evolution 3.24.5 (3.24.5-1.fc26) Mime-Version: 1.0 List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --=-8QZK5FZUUtfuIsC3ovfP Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Wed, 2017-10-04 at 15:36 -0500, Don Seiler wrote: >=20 > It's pointing to the newly installed version instead of the version it th= e > 9.2 lib directory. There isn't any such file under /usr/lib64. So how is = it > even aware of that /usr/pgsql-9.6 version? There is a file under /etc/ld.so.conf.d directory, which does this magic. >=20 > Yep that sounds good for later, although can't really help me in this cas= e. > I guess I can set unix_socket_directory in 9.2 to use the new location bu= t > that requires a restart anyway, not ideal. >=20 > Would creating a symlink be a workaround? Would that cause issues with > server restarts? >=20 > Mind that this is only to prepare for the upgrade. We aren't planning to > run both 9.2 and 9.6, and eventually 9.2 would be removed. What happens when you use 9.2's psql? /usr/pgsql-9.2/bin/psql Regards, --=20 Devrim G=C3=BCnd=C3=BCz EnterpriseDB: https://www.enterprisedb.com PostgreSQL Consultant, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR --=-8QZK5FZUUtfuIsC3ovfP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEH8GKHNUOKtDEiyD22MM9/pLPbrUFAlnVU4cACgkQ2MM9/pLP brWUvg//Tmykt7B5UCZIEn/ko7EIqUjRqW/Qgzlbumrr3ozzNq4rM7BooItTUuTu IELpT74l+NdCsoQUj+GURa9UVdCgYUHW3yk5Nr2phvTql3he8k1B6LaP3m+VuqZb tiQPDCvQndvWqY+hwnIB14FED/kFPo9FytE4QE+L6fWrUa9I+8Cok04UhPpYGng3 i4MBBT+PzaKsCfH/4GVeIq6+TIeJ9gcJOBbJLVmjH+HnJcJo5mg4oRBMM4mie1Y6 XVhTTU6unNaML4xchB3dK5v6K1RpEvFU49LXeTsnqjUiitdlTdDtWrOaK1++ycol rfSTU11h2vOih/a2LZDYvDD2NWyI512cHkbcDTuCsk2ArWB3iXyYuXeJVQJForOi ju2cZI9iCFmlOtp3K13JFBAFAciWOCIwx9Z/Ls1UC1AbKANXWxk3W1BaNZSRBzfc +TG7Hw6vYb22sb6vfaNWwdsV5f+SYn/BbyFj8GfyvD+qf3hDhfmMYUYQbFdmXAtJ +3eXYeWeGT/J3xkUysTCVvrzvXA96Dlk5nO3sCjm7aEZORxl2/Piy4HZ60HlapJO iopHrY4B+F48QO8YmphRZ0Qzpq9QKQVgBCOOm54itKzdOR/96BwdZciW8V9bWztu me8l87/EqVWtGx9iXLzbHnl8JiGb1C1UAd15Qs/dRhKkWrkijG4= =xe6t -----END PGP SIGNATURE----- --=-8QZK5FZUUtfuIsC3ovfP--