Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m1x81-0005qq-Me for pgsql-hackers@arkaria.postgresql.org; Fri, 09 Jul 2021 20:29:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1m1x7z-0003z2-BK for pgsql-hackers@arkaria.postgresql.org; Fri, 09 Jul 2021 20:29:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m1x7y-0003yu-Sb for pgsql-hackers@lists.postgresql.org; Fri, 09 Jul 2021 20:29:39 +0000 Received: from mail-pl1-x631.google.com ([2607:f8b0:4864:20::631]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1m1x7u-00041v-BC for pgsql-hackers@postgresql.org; Fri, 09 Jul 2021 20:29:37 +0000 Received: by mail-pl1-x631.google.com with SMTP id d1so415696plg.0 for ; Fri, 09 Jul 2021 13:29:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=bA97UL2cBH+SU+WamTagvrecfukZOCLUdte9qvUgGps=; b=UHrM99xTQFM50320Jruajia1Z/F0fzYuAzKz1qxDGzUC26Ubu4No1ULLI37PmY/3Ca MjRy7nzuZHkFJb3V4dgeXKIWSmGXWkHSsAhlI0SSdcGkN/HhyJFGyGf5+vsY0N/SHYeB hvY81TtbwNRfx2BhqxNAjQ7v3m8qCAdmR9InQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=bA97UL2cBH+SU+WamTagvrecfukZOCLUdte9qvUgGps=; b=fF0tiOgr+yGsMfYjqBACxuFszSFCl1Mrp+6s1SD2cmuuf4q4ft0YUZNQTwBQ9LRs47 uimXFa2AWrP2J+kQ8pPjqZy4HwDA/58OwQIi3q7jtZEgi68ppdKu7rz5sJwWnw6Kn5Hu KPK9okjnp30+wnzQV2St4JQ6gEWDMxm6Vc+1gbYPbg74dPtSINyUPHN9MVKhn4cxK07I Hi1tEOLYtHtSdBeZfSpThqfsm/EBYHO5jXBPqyRKX3B7XMl487Fj1b7+SZN0EPyZ9FRe 1okubV9P78KFWZ6PM0nHf4ZoLSE4eZaOs1Kn6N2EpX7t2WDj4HQJa5GHB9CBDyZ6F8Qv xzow== X-Gm-Message-State: AOAM533tBbzRherqcvLmwyq5R+7Q1q6IyTOKkJrAt97JgxFAT3F7n8Ey 6DL+0rF0QEdcbLoa1YjTeTxLJA== X-Google-Smtp-Source: ABdhPJzHushQwwbRnMhQqHgPdREPzGGiDMNTE6Ay4aL3tkRdIw1wzPPUlYGhwew5JExE+kEx466wtg== X-Received: by 2002:a17:902:778f:b029:128:b3e1:15f8 with SMTP id o15-20020a170902778fb0290128b3e115f8mr32472643pll.14.1625862573127; Fri, 09 Jul 2021 13:29:33 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::46]) by smtp.gmail.com with ESMTPSA id cs1sm13424290pjb.56.2021.07.09.13.29.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Jul 2021 13:29:32 -0700 (PDT) Date: Fri, 9 Jul 2021 13:29:29 -0700 From: Noah Misch To: Tom Lane Cc: Alvaro Herrera , Michael Paquier , Jacob Champion , "pgsql-hackers@postgresql.org" , Daniel Gustafsson , info@cspug.cz Subject: Re: Preventing abort() and exit() calls in libpq Message-ID: <20210709202929.GA2963274@rfd.leadboat.com> References: <202107021459.7c2dkzyg5lua@alvherre.pgsql> <819502.1625239217@sss.pgh.pa.us> <20210703001639.GB2374652@rfd.leadboat.com> <1231771.1625321413@sss.pgh.pa.us> <1233492.1625323559@sss.pgh.pa.us> <20210703214658.GA2421985@rfd.leadboat.com> <1288324.1625352260@sss.pgh.pa.us> <20210709095952.GA2945708@rfd.leadboat.com> <2093118.1625839578@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2093118.1625839578@sss.pgh.pa.us> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jul 09, 2021 at 10:06:18AM -0400, Tom Lane wrote: > Noah Misch writes: > > On Sat, Jul 03, 2021 at 06:44:20PM -0400, Tom Lane wrote: > >> That'd require buildfarm owner intervention, as well as intervention > >> by users. Which seems like exporting our problems onto them. I'd > >> really rather not go that way if we can avoid it. > > > I like that goal, though we'll have to see how difficult it proves. As of > > today, a GNU/Linux user building against static OpenLDAP will get a failure, > > right? That would export work onto that user, spuriously. > > As a former packager for Red Hat, my response would be "you're doing it > wrong". Nobody on any Linux distro should *ever* statically link code > from one package into code from another, because they are going to create > untold pain for themselves when (not if) the first package is updated. > So I flat out reject that as a valid use-case. > > It may be that that ethos is not so strongly baked-in on other platforms. Packagers do face more rules than users generally. > But I'm content to wait and see if there are complaints before rescinding > the automatic test; and if there are, I'd prefer to deal with it by just > backing off to running the test on Linux only. Okay. > > We'd get something like 95% of the value by running the test on one Windows > > buildfarm member and one non-Windows buildfarm member. > > True. But that just brings up the point that we aren't running the test > at all on MSVC builds right now. I have no idea how to do that, do you? I don't. But coverage via non-MSVC Windows is good enough. > > ... A strategy not having either of those drawbacks would be to skip > > the test if libpq.so contains a definition of libpq_unbind(). > > I assume you meant some OpenLDAP symbol? Yeah, that was supposed to say ldap_unbind().