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 1tIdUN-00FYBb-F9 for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Dec 2024 00:43:35 +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 1tIdUK-00DwkW-NC for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Dec 2024 00:43:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tIdUK-00DwkO-CS for pgsql-hackers@lists.postgresql.org; Wed, 04 Dec 2024 00:43:33 +0000 Received: from mail-oo1-xc2c.google.com ([2607:f8b0:4864:20::c2c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tIdUI-000uyq-Aw for pgsql-hackers@lists.postgresql.org; Wed, 04 Dec 2024 00:43:32 +0000 Received: by mail-oo1-xc2c.google.com with SMTP id 006d021491bc7-5f201a932b2so2443661eaf.3 for ; Tue, 03 Dec 2024 16:43:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1733273008; x=1733877808; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=kKABBpx+ynqtebWOt5rySFdgnR2NdCTtmhi/t9XuCoc=; b=mls4tUDEZRr9XKBDBUsmCATJWM68AIMJR3i6oltRPIvaUB/rRVGbcOw+9/KZrjsFrI UbqHmap3fuhSQ+SfbeY9efKko1rtW1r+zWKsKLDo549PWlM+vbdHd0XF0GPRnFqx4fGD HlT8dSTFnRIiAraB0EmgU3tIDvdljRWCKPRh79IKVnrcG6cZrDUGTUWEsnFLeE3LHmF7 OQIJEjiCqD5YyEqrk96eTHzsXgnjQbDmDBf52cTlO2ZB/SJ1/9oH9E35UZLQa2HFQ1N4 Vdrrp0VsZp4qfEtbSlwRs/syIG9271MxlXxS8BDA3zWlgwHmw+IWAtKiWKr1yK//b2Op J+LA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733273008; x=1733877808; h=content-transfer-encoding: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=kKABBpx+ynqtebWOt5rySFdgnR2NdCTtmhi/t9XuCoc=; b=VZ3MpxLIAiE1u6tj4KcwEiMLpXDvpnV/Ql0xKE8rk97iB62T712N241ZVG5CMyna0+ YjwG5LAHWYnEQIk/PuYjKnyLzGT36PGfI1gmdPEvMX1QBFJAUu2HurNE2+/4kriPBLFE urDMUZ+alS3A1PhyHaVomA5wiXv6VLBEzl9adXZOb/vFsBiV2JVkfU2sgTo6ikLztKeh ydg2awwwP1wZQCZ3X+S00pBE05uDegBw674cxt2x6DGL938YjWwesc4W8nepe55c6r/w Gk0/id0zw0I8ZOOduKNISwLYgGlSm5cb20o9FCmFVmoy1RG5pumA5j1lQVsYAa6wHMHQ H+9Q== X-Gm-Message-State: AOJu0YxAG3jCG5rx/gadAnq2fYl/fdZW5G/eVp1xugKlhQI86oTtkmkv y7K9bQBxH/gA0t4GWjJkPVt6Qc+0RG5fpk6JAw1lOlSYAZYy8PrMQPtlPHw80xbu2MsmEY9cc8P a7jDzNfeQY2PMPnflgNyo+SjF8DYbYhZT6uETIthxaVsX95I= X-Gm-Gg: ASbGncvWboMk69InIHO7EhN+sTOAQizUqfqiBLO8SjdoD4gvumCLm4zURIONxZkWdLN /V/AElXLV/ZeSoM3eqbdYg2Lva35ETA== X-Google-Smtp-Source: AGHT+IE05AFJO9snlp5BYWTJvidsQAKyCo8iFZ+9yGPtP40XITpfu3FoYLprJbmaYTVaKdLQJKlQ1MjO0HfcNrc4bz0= X-Received: by 2002:a05:6820:1b85:b0:5e1:d741:6f04 with SMTP id 006d021491bc7-5f263d86e42mr1431780eaf.3.1733273008687; Tue, 03 Dec 2024 16:43:28 -0800 (PST) MIME-Version: 1.0 References: <1C81CD0D-407E-44F9-833A-DD0331C202E5@yesql.se> <88986722-5A72-4DEC-8750-BDBF67FF8C01@yesql.se> In-Reply-To: <88986722-5A72-4DEC-8750-BDBF67FF8C01@yesql.se> From: Jacob Champion Date: Tue, 3 Dec 2024 16:43:18 -0800 Message-ID: Subject: Re: Serverside SNI support in libpq To: Daniel Gustafsson Cc: Pgsql Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, Dec 3, 2024 at 5:58=E2=80=AFAM Daniel Gustafsson = wrote: > > Have you seen any weird behavior like this on your end? I'm starting > > to doubt my test setup... > > I've not been able to reproduce any behaviour like what you describe. Hm, v2 is different enough that I'm going to need to check my notes and try to reproduce again. At first glance, I am still seeing strange reload behavior (e.g. issuing `pg_ctl reload` a couple of times in a row leads to the server disappearing without any log messages indicating why). > > On the plus side, I now have a handful of > > debugging patches for a future commitfest. > > Do you have them handy for running tests on this version? I'll work on cleaning them up. I'd meant to contribute them individually by now, but I got a bit sidetracked... Thanks! --Jacob