From: Justin Pryzby <pryzby@telsasoft.com>
To: Christopher Wilson <chris.wilson@cantabcapital.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Cc: Steven Winfield <Steven.Winfield@cantabcapital.com>
Subject: Re: Possible optimisation: push down SORT and LIMIT nodes
Date: Wed, 30 May 2018 14:09:44 -0500
Message-ID: <20180530190944.GA25841@telsasoft.com> (raw)
In-Reply-To: <20180530190231.GH5164@telsasoft.com>
References: <BCCA73C2165E8947A2E786EC482564DE01301FB8F2@CCPMAILDAG03.cantab.local>
<20180530190231.GH5164@telsasoft.com>
On Wed, May 30, 2018 at 02:02:31PM -0500, Justin Pryzby wrote:
> For diagnostic purposes, I was able to to vastly improve the query runtime with
> a CTE (WITH):
I realized this was broken as soon as I sent it (for the essential reason of
discarding rows before having sorted them). Sorry for the noise.
Justin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pryzby@telsasoft.com, chris.wilson@cantabcapital.com, Steven.Winfield@cantabcapital.com
Subject: Re: Possible optimisation: push down SORT and LIMIT nodes
In-Reply-To: <20180530190944.GA25841@telsasoft.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox