Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uT4d7-00H2ei-MS for pgsql-novice@arkaria.postgresql.org; Sat, 21 Jun 2025 20:16:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uT4d5-00922f-OF for pgsql-novice@arkaria.postgresql.org; Sat, 21 Jun 2025 20:16:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uT4d5-00922W-Fm for pgsql-novice@lists.postgresql.org; Sat, 21 Jun 2025 20:16:00 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uT4d4-003HQr-1c for pgsql-novice@lists.postgresql.org; Sat, 21 Jun 2025 20:15:59 +0000 Received: by mail-ej1-x62d.google.com with SMTP id a640c23a62f3a-acbb85ce788so555938566b.3 for ; Sat, 21 Jun 2025 13:15:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1750536955; x=1751141755; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=csXOk2l9i57DrXIC61MyEQkAWlS+QQHpRpzu4yCaPXs=; b=YX0GU78OcR0sSMCik9wnCGOX38xmR++cvtxQZflo275aByOHoaf5ba0Vu04JlSOV7H 1LhGZr2EOCl1o/M2QiJs/p+WUcGk+g5mxujDAagAalQYZuIjhDbnv7BvSvXqLUkzHctl zQu7Ok0bU187hLdihBfUVUN/oKbGfk8c/l1H/JDILmuKenlCDJDCg9aw4LFn2vT2w/uc REZF5aFUomEZ/qIU6wbsg5sybpN0RgNriMxLF22wIfKEzDo9rv4mC1y5a+98OASalhkw 0/JbcPqcMUaH7xaNEHHAZMAsijN2Kd9O0e+Kdx3bqIEh1QkvPt+vtUkE6jaAV9vsYM81 Xoxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750536955; x=1751141755; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=csXOk2l9i57DrXIC61MyEQkAWlS+QQHpRpzu4yCaPXs=; b=UrPKXXeDCH33gtpRGw9yScH844xzRUjYK0phNmW13UFc/4Q5msbmkyURjbVhrkKy+G 5T8NlYQm0gYYITOqNdCTgInRg4oeK2VKgX7/ghI7DRAcmjHvTOhZzAlWsrVGJvh13wj1 hMbUsONWpV3UAIll0kOY84c7Vjhwykzsf3vWhDv8EaD8yMOvbVFxXbS+/eAXrwRyTZAA R+Npzt7q5267p5WoV+9//g8TLXLQLQEuskWe/K586I9CtlYAGFuXCwNdlioHl7bhU+b1 Swzjie7Mg0QkwERj0LxPDv3p/a4JTfnXEIGxwyemA+83/iDQy0PaSY+J5Ge8zYJgqWdi P+Ew== X-Gm-Message-State: AOJu0YzdOb7rsaUAyzYUJcironpCKeZu72mvNKUdmJYDK/cYSTcGcOlA tpAKrXDXtw+pKnpnZOnxqB/Il0bWFYUeL4Bz3haJLU9a4x1FQfKzQQ9gbrsa6tY3cYQys9Ilgco +8nfdLJR9n+17+zKUMEB3Xmxk/LhpnmwLiA== X-Gm-Gg: ASbGnctnCHfgLo1nlGdMM5NItXelWS1yiS6dwej3/YqGGgfVz2PNqmIB/Djcf6PP1u5 1etZQRGLbXa7o9h3u5JFktSUm5bpfmog5jCo5OR5GSsoF0q0ehkYx5gY6CvKLPWwAuNIusxDxOC KqGqbLtPJx23OQwrlmsO7wUQuSduQcyw4GCGdaTaGczE1W1ImgoKWFU8Y4GXcaMwd1Ac2W6tebH H7G X-Google-Smtp-Source: AGHT+IHtsBfS/2nSNAzF/2lYYCoreq/Z9ZMWwZOZkol0bC1WBw7O5Vzv01R2iJua3VMapYKwLjxGKfDRNbUzfrnkn6U= X-Received: by 2002:a17:907:7e92:b0:ade:1863:6ff2 with SMTP id a640c23a62f3a-ae057c13c6amr697841366b.52.1750536954649; Sat, 21 Jun 2025 13:15:54 -0700 (PDT) MIME-Version: 1.0 References: <2791030.1750536336@sss.pgh.pa.us> In-Reply-To: <2791030.1750536336@sss.pgh.pa.us> From: Sherman Willden Date: Sat, 21 Jun 2025 14:15:43 -0600 X-Gm-Features: AX0GCFuUKgLE6Jr83YYtJBbi3amuEr2BD8eQA-C02V5c-en44I7_CAmM8MDSh-8 Message-ID: Subject: Re: been away awhile but postgresql doesn't work for me now To: Tom Lane Cc: pgsql-novice@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000591edb06381aa55e" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000591edb06381aa55e Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks, I'll look into it. On Sat, Jun 21, 2025 at 2:05=E2=80=AFPM Tom Lane wrote: > Sherman Willden writes: > > Basic complaint: polgresql 16 doesn't function as I think it should > > First Error: postgresql psql server connection failed error > > Second Error: Even after modifying /etc/postgresql/16/main/pg_hba.conf > > to trust the system is asking for postgres password. > > First question: did you restart the PG server, or at least do > "pg_ctl reload", after modifying pg_hba.conf? It won't notice > config file changes till you do. > > Second question: are you sure there's only one PG installation > on the machine? You might be connecting to a different installation > than you think you are. > > None of this stuff has changed greatly in the past couple of years. > My guess is that you don't have the system configured quite the > same as you did before. > > regards, tom lane > --000000000000591edb06381aa55e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, I'll look into it.=C2=A0

On Sat, Jun 21, 2025 at 2:05=E2=80=AFPM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Sherman Willden <sherman.willden@gmail.com>= writes:
> Basic complaint: polgresql 16 doesn't function as I think it shoul= d
> First Error: postgresql psql server connection failed error
> Second Error: Even after modifying /etc/postgresql/16/main/pg_hba.conf=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0to trust the sys= tem is asking for postgres password.

First question: did you restart the PG server, or at least do
"pg_ctl reload", after modifying pg_hba.conf?=C2=A0 It won't = notice
config file changes till you do.

Second question: are you sure there's only one PG installation
on the machine?=C2=A0 You might be connecting to a different installation than you think you are.

None of this stuff has changed greatly in the past couple of years.
My guess is that you don't have the system configured quite the
same as you did before.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 regards, tom lane
--000000000000591edb06381aa55e--