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 1qtG2d-00BdA8-EX for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Oct 2023 23:33:31 +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 1qtG2a-00A5wp-1B for pgsql-hackers@arkaria.postgresql.org; Wed, 18 Oct 2023 23:33:28 +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 1qtG2Z-00A5wh-FY for pgsql-hackers@lists.postgresql.org; Wed, 18 Oct 2023 23:33:28 +0000 Received: from mail-yw1-x1133.google.com ([2607:f8b0:4864:20::1133]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qtG2X-001AJy-0Q for pgsql-hackers@lists.postgresql.org; Wed, 18 Oct 2023 23:33:26 +0000 Received: by mail-yw1-x1133.google.com with SMTP id 00721157ae682-5a7be88e9ccso93058667b3.2 for ; Wed, 18 Oct 2023 16:33:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1697672004; x=1698276804; darn=lists.postgresql.org; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=7MTomsGpRBJlX3PiklJpJPM9tRSaEy/RGR1oweCPVDo=; b=QIK0iEov9hAoBh/YZZWhvNFlwV2dZghqTM8zR/7wj8yBQ1J/n5iMi3GUD2bvLyPHxt gnVbj0qG5vsJYdHP7qj0bn/XUHhBXAD4wFfwVeVm2X54nsA51YY3QdwNgOHruDWMWhs2 HVhXQE2kZGEdfEsx7iC7w7YzjvDkEfmIZ0HSY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697672004; x=1698276804; h=user-agent:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=7MTomsGpRBJlX3PiklJpJPM9tRSaEy/RGR1oweCPVDo=; b=Lp2myEji4BrQ+z3UUoyGtBiFUXAx/p2rXGODpxUCanpsg2NMhtk3hiCQy6ydF5LWBI i7MLGqqDR1Uo77D5Qo7yMLbwaX0EYu3ERMiTi3Y34538eGrH0nq+/s3x+tSKyAq9HrOg K6E1qarv4gmybERXQBKhXQJjkzbuC2lTNsLGL1zXt0RnReNn1e/Rlf5eLYL6GOGPi0nr ZHf2sb2fAnjgelytpJ/4xExPsFteTVKroa8JmNZXu/xKuatv1OluE8jsoet2I0SYfDxX Q+bxKiOtvnwt6jC9Iw3nXasSaszQQLGkp01sgVYmGE5tLeRS1YUfxg+ahvq58d9ZMB5J lOFw== X-Gm-Message-State: AOJu0YwQRolq97w3xAHs+LhB+J8vDSeAZQxdmRhrSJIgOfG0uvy05Ga5 vb0c9PcKPHqLOzVO85fGGZwbsQ== X-Google-Smtp-Source: AGHT+IFsc3j4i++SVAzcRrD1dgkZRIWMd0CGEMEF1w7o3erOZr42l6ff7Su6Hlwq92n8Gcyb8eu8kg== X-Received: by 2002:a25:cc4e:0:b0:d9a:e2d3:74ff with SMTP id l75-20020a25cc4e000000b00d9ae2d374ffmr871708ybf.19.1697672004290; Wed, 18 Oct 2023 16:33:24 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::2e]) by smtp.gmail.com with ESMTPSA id z4-20020a25ad84000000b00d815cb9accbsm1665013ybi.32.2023.10.18.16.33.22 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Oct 2023 16:33:23 -0700 (PDT) Date: Wed, 18 Oct 2023 16:33:20 -0700 From: Noah Misch To: Tom Lane Cc: Robert Haas , Thomas Munro , Michael Paquier , Vik Fearing , cary huang , pgsql-hackers@lists.postgresql.org Subject: Re: Add support for AT LOCAL Message-ID: <20231018233320.cc@rfd.leadboat.com> References: <2726901.1697556666@sss.pgh.pa.us> <2820407.1697561128@sss.pgh.pa.us> <2995973.1697583273@sss.pgh.pa.us> <3001171.1697585525@sss.pgh.pa.us> <3122652.1697644948@sss.pgh.pa.us> <3154146.1697661946@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3154146.1697661946@sss.pgh.pa.us> User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Oct 18, 2023 at 04:45:46PM -0400, Tom Lane wrote: > > On Wed, Oct 18, 2023 at 12:02 PM Tom Lane wrote: > >> Probably. Independent of that, it's fair to ask why we're still > >> testing against xlc 12.1 and not the considerably-more-recent xlclang, > >> or at least xlc 16.1. (I also wonder why we're still testing AIX 7.1 > >> rather than an OS version that's not EOL.) > The machine belongs to OSU (via the gcc compile farm), and I see > that they have another one that's POWER8 and is running AIX 7.3 [1]. > So in principle the buildfarm animals could just be moved over > to that one. > > Perhaps Noah has some particular attachment to 7.1, but now that that's > EOL it seems like we shouldn't be paying so much attention to it. > My guess is that it's still there in the compile farm because the gcc > people think it's still useful to have access to POWER7 hardware; but > I doubt there's enough difference for our purposes to be worth dealing > with a dead OS and ancient compiler. No particular attachment. From 2019 to 2023-08, hoverfly tested xlc16 on AIX 7.2; its run ended when cfarm119's owner replaced cfarm119 with an AIX 7.3, ibm-clang v17.1.1 machine. Since 2015, hornet and mandrill have tested xlc12 on AIX 7.1. That said, given your finding that later xlc versions have the same code generation bug, the choice of version is a side issue. A migration to ibm-clang wouldn't have prevented this week's xlc-prompted commits. I feel the gravity and longevity of xlc bugs has been out of proportion with the compiler's contribution to PostgreSQL. I would find it reasonable to revoke xlc support in v17+, leaving AIX gcc support in place. The main contribution of AIX has been to find the bug behind commit a1b8aa1. That benefited from the AIX kernel, not from any particular compiler. hornet and mandrill would continue to test v16-. By the way, I once tried to report an xlc bug. Their system was tailored to accept bugs from paid support customers only. I submitted it via some sales inquiry form, just in case, but never heard back.