Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1icABu-0001iD-C6 for pgsql-admin@arkaria.postgresql.org; Tue, 03 Dec 2019 15:34:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1icABt-0003zC-44 for pgsql-admin@arkaria.postgresql.org; Tue, 03 Dec 2019 15:34:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1icABs-0003uc-IX for pgsql-admin@lists.postgresql.org; Tue, 03 Dec 2019 15:34:16 +0000 Received: from mail-wr1-x435.google.com ([2a00:1450:4864:20::435]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1icABo-0006iy-GB for pgsql-admin@lists.postgresql.org; Tue, 03 Dec 2019 15:34:15 +0000 Received: by mail-wr1-x435.google.com with SMTP id y11so4209343wrt.6 for ; Tue, 03 Dec 2019 07:34:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zunibal-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=TY2gDtvqO0B8Kn7TDSHQRI0gITxzMPrZXuQX1n3Lc5I=; b=v5uetmDBGqWNYqHiNR6xEBFNMXIuyIhXk+sx9OSLPHxJEPvHWkyuWY0W7aMDRfA8Fi auNewdtkwJ+OfZ6WRovM+wANCtFpwRFY0yI3bcewObtB7q5q1UiOh3Qh383OGd4mWQA2 xg2cfWOVsveBEItwoOzTf8HDqXKj0gOB1g530gFhlR640XgXFr9cDEaCtEbfmNcJclk6 Ks+f2yGN6UYsskiaNx+32fPtfc/Vskyfi19yI6IUaqfUeOXsd3WJ9PJELyF5dAguWpUr cxR/JZH+6zsyzu1ZxHqzSiQtXri2MjyIev4nWZvtGHQZBgAfirBfGPQSJLajR7zDv5r1 r3CA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=TY2gDtvqO0B8Kn7TDSHQRI0gITxzMPrZXuQX1n3Lc5I=; b=Ws0GzDVh6nLSmdYOkP2z4BdelfH7Q3p7bMSAhoG8xjT6xBLImNHIgN1D8XD37LOZoA sood28i94MirA+teLxs9cVsHmdQK3awnAzpIRXYP8/smG2POEywGTDsj4SDzq66DxKXv 6jgQuQpEnEyn+sLoldcqJrKqetZHq0V3tv2jlPqhDyJiCEyKzAHizhfPkuFfWn+uwIfF AsoMCDzPin8Q1LPXmj+49k+Jp/MotNQR8Z0uIDRmiqLhYR38vaveelx2cXFhHiCx1t4I KEyuCt011NKRg8jBPTrPAxKY7LO/+NyGe42zVnXr7kUyRmnQJqf3ehz03x960qmZ5bpS hJYw== X-Gm-Message-State: APjAAAW7XFPnLB6EtGxatdKl0CA3Cw7mvqTxp80dZSVpN8+5L4N/PVpp t8YgAxZ6jjeL3aenuQOFBjuUpH4atNI= X-Google-Smtp-Source: APXvYqwD47Hnan9iwOXv2AgzDXbJrx6sP9cJIKCFacxqWKga7kNJizKtPdOq7Reg6LOTBuGLP5sdcQ== X-Received: by 2002:adf:d183:: with SMTP id v3mr5899915wrc.180.1575387246135; Tue, 03 Dec 2019 07:34:06 -0800 (PST) Received: from [192.168.3.150] ([176.222.91.85]) by smtp.gmail.com with ESMTPSA id q15sm4096698wrr.11.2019.12.03.07.34.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Dec 2019 07:34:05 -0800 (PST) Subject: Re: Should I care about this error "failed to link /usr/bin/psql [...] exists and it is not a symlink"? To: Tom Lane Cc: pgsql-admin@lists.postgresql.org References: <516a1fbf-2323-4278-86f0-e7e4886f73e5@zunibal.com> <32105.1575386099@sss.pgh.pa.us> From: Ekaterina Amez Message-ID: Date: Tue, 3 Dec 2019 16:34:04 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1 MIME-Version: 1.0 In-Reply-To: <32105.1575386099@sss.pgh.pa.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi Tom, El 3/12/19 a las 16:14, Tom Lane escribió: > Ekaterina Amez writes: >> I'm installing postgres 9.6 in a CentOS 7 computer that already has >> postgres v9.2 installed (version that comes with CentOS installer) and >> I've seen the message of this mail's subject. >> ... >> failed to link /usr/bin/psql -> /etc/alternatives/pgsql-psql: /usr/bin/psql exists and it is not a symlink >> ... > I believe the issue here is that you've got Red Hat's postgresql packages > installed, As I've mentioned, this Postgres version comes with CentOs installation, so I guess you're right. > and they're not set up to participate in alternatives > switching. I'd suggest removing those packages By "removing those packages" you mean uninstall v9.2? This is a test computer and it's not a problem, but I'm afraid this is going to happen also in production server, by doing this won't be my cluster be unavailable? > --- having them installed > alongside PGDG postgres packages is going to lead to nothing but grief. > > regards, tom lane So what's happening is that I have installed a RH version of Postgres instead an official one? Am I right? Regards, Ekaterina