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 1sdvu2-002Mfn-W0 for pgsql-bugs@arkaria.postgresql.org; Tue, 13 Aug 2024 18:05:50 +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 1sdvu1-005RON-Bg for pgsql-bugs@arkaria.postgresql.org; Tue, 13 Aug 2024 18:05:49 +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 1sdvu1-005ROF-1S for pgsql-bugs@lists.postgresql.org; Tue, 13 Aug 2024 18:05:49 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sdvtu-004ZxQ-Bx for pgsql-bugs@lists.postgresql.org; Tue, 13 Aug 2024 18:05:47 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 47DI5YnM045863; Tue, 13 Aug 2024 14:05:34 -0400 From: Tom Lane To: Cameron Vogt cc: "pgsql-bugs@lists.postgresql.org" Subject: Re: TLS session tickets disabled? In-reply-to: References: <6aca4816-be12-4f54-9eba-8c9b55cdc801.094840f8-2c1e-4d5a-9984-8ac00be38080.1f3171ea-77be-4931-bfa7-87210a40ff9f@emailsignatures365.codetwo.com> Comments: In-reply-to Cameron Vogt message dated "Mon, 12 Aug 2024 21:19:22 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <45861.1723572334.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Tue, 13 Aug 2024 14:05:34 -0400 Message-ID: <45862.1723572334@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Cameron Vogt writes: > I recently updated one of my PostgreSQL databases to 16.4. Since updatin= g, I am unable to refresh Power BI reports that rely on the database. The = error message in my PostgreSQL server's log file is "could not accept SSL = connection: session id context uninitialized". I looked up the error messa= ge and found my issue in another mailing list: https://www.postgresql.org/= message-id/CADT4RqBU8N-csyZuzaook-c795dt22Zcwg1aHWB6tfVdAkodZA%40mail.gmai= l.com. > After reading the old thread, it looks like the resolution was to make t= he PostgreSQL server pass SSL_OP_NO_TICKET to SSL_CTX_set_options. I belie= ve the 16.4 update has resurrected this issue. In the 16.4 release notes, = I found a bullet point that says: > "Disable creation of stateful TLS session tickets by OpenSSL. > This avoids possible failures with clients that think receipt of a sessi= on ticket means that TLS session resumption is supported." > Would it be possible to get this change reverted in the next update? What is your argument that it's not the client that is broken? AFAIK, it should not be requiring a session ticket to exist. regards, tom lane