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 1qsFgE-007IGX-SY for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Oct 2023 04:58:14 +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 1qsFgC-00FkjY-Eh for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Oct 2023 04:58:13 +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 1qsFgB-00FkjQ-Uu for pgsql-hackers@lists.postgresql.org; Mon, 16 Oct 2023 04:58:12 +0000 Received: from mail-yb1-xb33.google.com ([2607:f8b0:4864:20::b33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qsFg9-000hOx-TU for pgsql-hackers@lists.postgresql.org; Mon, 16 Oct 2023 04:58:11 +0000 Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-d9a3d737d66so4257697276.2 for ; Sun, 15 Oct 2023 21:58:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1697432289; x=1698037089; 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=ldRa/zzcY83X9ZfzI0sWnCFDCdoqpZ9T8q+M2LLgJbg=; b=EwrkSmSzy4NWQql/TQy50nsoyFpL3BmRoLIcxY8iXgKGV7rAEJjUodmSOgg+2vtAL1 qBnuc5yKMGzo+Zq/2rhqw8PszG3vxesxfKFZHrsElBminvGxWl3/equ0ms1LF5pt/CZx Mjmudp5SBfLf3iaNwSNkIyhjWlEnbir9rjYPI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697432289; x=1698037089; 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=ldRa/zzcY83X9ZfzI0sWnCFDCdoqpZ9T8q+M2LLgJbg=; b=VsDXaQMQCbEMMeta3r+WgQ2QlftyMTK5hIZ7G/Ms/xb1ElAAPTJTfmZJEhIPI7KUaS dNvkPR6FpCcnqUP/ZX9jidZUG+z1blAx5cE7osifzBYRJ950wU6E4C5lk0y0jBV0Coax QMnS6qFy37ccx5cnBctFZlDWkJJzbSjotjsdspEN4gV6iqlNieLTsfBuTJjZlUaIjesq rhChKKMIBE5za+cTO29OJ9xiwiv9QcTG+nB0QMdI9/4PqmoeVJJ42IlQoMlb7vHSdJbm C3YiGFfQLvOacCQ7sOQrc2/WO9Ldwp74qvUFcsABnTGf55a8A46jzyXwPt2S+wdwt8ef rD7w== X-Gm-Message-State: AOJu0YxMCwCXs8W330TxAZZDqSKW2c7ruYsSm7KRML7sWlK8p1UgywTn dLKc9O4QWcSmGKT0P3IPpPTFng== X-Google-Smtp-Source: AGHT+IGoubzv8WL54CbyAKxQjZtnL4Lg5xHn91Xnha47W71I5mhu9gsbgFix20l0h9rzRBJkqeZHAQ== X-Received: by 2002:a25:8248:0:b0:d9a:5859:bf14 with SMTP id d8-20020a258248000000b00d9a5859bf14mr15611667ybn.64.1697432289193; Sun, 15 Oct 2023 21:58:09 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::2e]) by smtp.gmail.com with ESMTPSA id 66-20020a250d45000000b00d8168e226e6sm2440763ybn.47.2023.10.15.21.58.07 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 15 Oct 2023 21:58:08 -0700 (PDT) Date: Sun, 15 Oct 2023 21:58:04 -0700 From: Noah Misch To: Tom Lane Cc: Thomas Munro , Michael Paquier , Vik Fearing , cary huang , pgsql-hackers@lists.postgresql.org Subject: Re: Add support for AT LOCAL Message-ID: <20231016045804.c0@rfd.leadboat.com> References: <2129576.1697407071@sss.pgh.pa.us> <2188264.1697425365@sss.pgh.pa.us> <2191749.1697427017@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: <2191749.1697427017@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 Sun, Oct 15, 2023 at 11:30:17PM -0400, Tom Lane wrote: > Thomas Munro writes: > > On Mon, Oct 16, 2023 at 4:02 PM Tom Lane wrote: > >> I'm having a hard time not believing that this is a compiler bug. > >> Looking back at 8d2a01ae12cd and its speculation that xlc is overly > >> liberal about reordering code around sequence points ... I wonder > >> if it'd help to do this calculation in a local variable, and only > >> assign the final value to result->time ? But we have to reproduce > >> the problem first. > > > If that can be shown I would vote for switching to /opt/IBM/xlc/16.1.0 > > and not changing a single bit of PostgreSQL. > > If switching to 16.1 removes the failure, I'd agree. It's hard > to believe that any significant number of users still care about > building PG with xlc 12. Works for me. I've started a test run with the xlc version change.