Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iK4Ti-0006Od-6c for pgsql-hackers@arkaria.postgresql.org; Mon, 14 Oct 2019 17:49:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iK1Uw-0004OA-Sv for pgsql-hackers@arkaria.postgresql.org; Mon, 14 Oct 2019 14:38:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iK1TY-0004ND-QD for pgsql-hackers@lists.postgresql.org; Mon, 14 Oct 2019 14:37:33 +0000 Received: from mail-io1-xd2b.google.com ([2607:f8b0:4864:20::d2b]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iK1TV-0005g0-1u for pgsql-hackers@lists.postgresql.org; Mon, 14 Oct 2019 14:37:31 +0000 Received: by mail-io1-xd2b.google.com with SMTP id c6so38280591ioo.13 for ; Mon, 14 Oct 2019 07:37:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=2LnoLuWlqPx1ba8oyYUmbzMGTxsWno1u8t87nbQdDkY=; b=yzV+zRVjUkOzkyCbWtafzi/b8/BLYYaexxSmxLlFcE5oPg6rB2QuiuZprzMx6DWuK1 VjyKuSSeIoq7/NhEIji5XxzLIQOuUxPWZQnIWrU7jVv5e0VykVLESAyZOF7rwNKOxYQK 33HGR1RLlZVSi20/gTWcXHsV/N/qm3rnNnzuWvzSMiN+UdKFZYIGXIIp+lNpYd0WhHa+ oAvHxB3w9TISn9ZxPElOu5o0Bb3P5qCew9p5A3TGNJGYkAwEBfFNQumI0nPmTWwD8Lx4 iWaILF3ti/yok6jHB6z60E/qmJ6rsiZfRXuAQHwX7ZIOF+/Y7USGFammwsNbexeFX7zN g53g== 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=2LnoLuWlqPx1ba8oyYUmbzMGTxsWno1u8t87nbQdDkY=; b=CqmbRReSVDXDs0CIWStWwzLEN1DcftmQvGdOHXfx4/7JeoVxeMRh4OcQ/vfiY1yXxU JZoIeq2i7NtZCVEslZTo8LWuU+L21gfec1R1ovQykRamwfcNo6bPuY4Pa9xmOyd4MLo1 NHy9emTVjMBV297KomCfA3FAo0yrvLRemU7bmA/JVUpyKRBhRtJOb/Zx4ZKhlptgO8kG WjoIuCpo+p7pWAnSzye48TZi0GYsJWd7JKnrA8VQfjr3tViLfaHbRiLGLnAv0cj+tvl/ Pei4wqe7zhKf1HGDPquT62pOUaElzP0TKLqFKIO67D22ak6A8MFLm/JZVZnzSDDlkqM2 ZwOw== X-Gm-Message-State: APjAAAUKYjJPy4NXVTXjnGrZ11GlsOZoFix3KRShfC39qz48BV7u1Yny BEVqw/yeBa96osE274iQdMqD2w== X-Google-Smtp-Source: APXvYqz1SYv01R8opFvkqUY7CdN5Z4OEeSBscKtn9bqN0mEKr5atJ4b78OPTiz+ZEvmAKIf4rVs3ZQ== X-Received: by 2002:a5d:9e09:: with SMTP id h9mr37796155ioh.83.1571063847988; Mon, 14 Oct 2019 07:37:27 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id c4sm1175349ilh.32.2019.10.14.07.37.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Oct 2019 07:37:26 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id 512008011CB; Mon, 14 Oct 2019 09:37:25 -0500 (CDT) Date: Mon, 14 Oct 2019 09:37:25 -0500 From: Justin Pryzby To: Tom Lane Cc: pgsql-hackers@lists.postgresql.org, Amit Langote Subject: Re: v12.0: ERROR: could not find pathkey item to sort Message-ID: <20191014143725.GD3599@telsasoft.com> References: <20191011143703.GN10470@telsasoft.com> <17486.1570805317@sss.pgh.pa.us> <20191012222346.GB4475@telsasoft.com> <16802.1570989962@sss.pgh.pa.us> <20191013183029.GI4475@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191013183029.GI4475@telsasoft.com> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sun, Oct 13, 2019 at 01:30:29PM -0500, Justin Pryzby wrote: > BTW it probably should've been documented as an "Open Item" for v12. https://commitfest.postgresql.org/25/2278/ I realized possibly people were thinking of that as a "feature" and not a bugfix for backpatch (?) But, my issue is a query which worked under v11 PWJ but fails under v12 (apparently broken by d25ea01275). In my mind, if the planner doesn't support that query with PWJ, I think it should run without PWJ rather than fail. Justin