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 1sU6Yn-000Tic-4X for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 15:27:16 +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 1sU6Yl-002EWq-B5 for pgsql-general@arkaria.postgresql.org; Wed, 17 Jul 2024 15:27:15 +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 1sU6Yl-002EWi-02 for pgsql-general@lists.postgresql.org; Wed, 17 Jul 2024 15:27:15 +0000 Received: from mail-oo1-xc2a.google.com ([2607:f8b0:4864:20::c2a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sU6Yi-0002Zn-Li for pgsql-general@lists.postgresql.org; Wed, 17 Jul 2024 15:27:14 +0000 Received: by mail-oo1-xc2a.google.com with SMTP id 006d021491bc7-5ce74defe43so619329eaf.2 for ; Wed, 17 Jul 2024 08:27:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1721230032; x=1721834832; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=kQTqWz/j7TiOXFcAZt/g4A5uoo5o751d1BlONFStCe4=; b=JbHOdHyHPH5Cy/Xf3q1FTEjBpB4ex2wJcgpwLKXwZV9NyGSeTqlZak2p0IX1cVg60o 8fASlYFCjn3PGMDBKg5MNDTdZqjLV64x2KO3NjX7EyhF3OYbel32JjvMQ5h6XCym8dWX xhqohj45jSYDqLqURXgiEeaD9G5SX9nZSX3E+95q/WBSfRmYLMBbAp6bV2C9kUUhyMYo WdZqzx7y2Qxyubhc7GjbTE4L9u66N+aVIQXQjmuIkYzRQNdk1RYCBtBA8pkL5dOuFvzU uVCUSWnBV7kNtPqY8DTKs5ebDGI2gDlwZgqxJurSNSM3B4zNVs0t9uyxCeb2mlBol58y cbuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1721230032; x=1721834832; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=kQTqWz/j7TiOXFcAZt/g4A5uoo5o751d1BlONFStCe4=; b=RcH6y+Bd/qZW77zVPT/nRl8YNFvD3AIxIgi/oXyFB+fvoQU50FAC7+PwO6/5NWVH1O 7TSIyHtZWw0yiJHzN1O806ubKgUDA5/gm083BiJs5229XMFvdUY0PMohJO9FavirhMaN S8ybLELenp4MfGhWU3hFYbGGBXVd8S2epGj0fJ921kvPZslURVMBMgEz8gXEoa2pFNfm CjtWJ4nhNy9cmLi92cUkXR5hKZdgB/BiwAJH3cDPWhi9X5JkbJQBL+o0olDubL2L/XCB ItXq6cWhRvtp7rBmimG9dWRl/zi1yHP1CEHnk4VZY9si2q5TiJhntOBu2DzWbjToZncV eq9g== X-Gm-Message-State: AOJu0YyGyou/C8LBZxDFmiZ80pRNSCwjicyqtJmwW186oHni8X9diQ8p p/wqLGMkaciniyTTvTMqgmJSZ7787xPFeUrFibaesaGyBF47UBZK1heKKNLLFAp48Rsvy82jZWy hkY/KTdW9ZVQnjoRV4S8Wm2q3vX8dZA== X-Google-Smtp-Source: AGHT+IFh7BSpG/FtPHbGL7fjlD+VdpiSu0vY06liT0/eHpI2TikWsIfpIRrNg8l2WMPWUuDOgEWTk7KWLvS+JKA1E9c= X-Received: by 2002:a05:6820:994:b0:5c6:658c:a9f6 with SMTP id 006d021491bc7-5d41a4c1e53mr2962410eaf.2.1721230031713; Wed, 17 Jul 2024 08:27:11 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:760a:0:b0:539:aa10:6c7 with HTTP; Wed, 17 Jul 2024 08:27:11 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Wed, 17 Jul 2024 08:27:11 -0700 Message-ID: Subject: Re: Issue with configuration parameter "require_auth" To: "Gaisford, Phillip" Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000009dffbc061d731805" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000009dffbc061d731805 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, July 17, 2024, Gaisford, Phillip wrote: > I am having trouble using require_auth (https://www.postgresql.org/ > docs/16/libpq-connect.html#LIBPQ-CONNECT-REQUIRE-AUTH). > > > > Using golang sqlx.Connect on the client side, the connection fails and my > Postgresql 16 server logs the following: > > 2024-07-17 14:42:07.285 UTC [115] FATAL: unrecognized configuration > parameter "require_auth" > > > > What could the issue be? > > > Seems like a bug or version mis-match in the client library. That is a new option in v16 so it may not be handled properly. That option is client-only, the client should not be sending it to the server, which the error message indicates it is. Unless you can reproduce with psql you=E2= =80=99ll need to check your installation environment (maybe you only have v15 or less client libraries installed?) or file a bug with the driver project. David J. --0000000000009dffbc061d731805 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wednesday, July 17, 2024, Gaisford, Phillip <phillip.gaisford@hpe.com> wrote:

I am having trouble using require_auth (https://www.postgresql.org/docs/16/libpq-conne= ct.html#LIBPQ-CONNECT-REQUIRE-AUTH).

=C2=A0

Using golang sqlx.Connect on the client side, the connection fails and my= Postgresql 16 server logs the following:

2024-07-17 14:42:07.285 UTC [115] FATAL:
=C2=A0 unrecognized configuration parameter "require_auth&= quot;

=C2=A0

What could the issue be?

=C2=A0


Seems like a bug or version mis-match in the client librar= y.=C2=A0 That is a new option in v16 so it may not be handled properly.=C2= =A0 That option is client-only, the client should not be sending it to the = server, which the error message indicates it is.=C2=A0 Unless you can repro= duce with psql you=E2=80=99ll need to check your installation environment (= maybe you only have v15 or less client libraries installed?) or file a bug = with the driver project.

David J.

--0000000000009dffbc061d731805--