Re: [PATCH] Push limit to sort through a subquery

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Douglas Doole <dougdoole(at)gmail(dot)com>
Cc: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Push limit to sort through a subquery
Date: 2017-08-21 18:43:05
Message-ID: CA+TgmobzYgTYCDzA8DrjJQ1jksFVRXTXewRyuS3JbTKFGV8ySg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 18, 2017 at 4:08 PM, Douglas Doole <dougdoole(at)gmail(dot)com> wrote:
>> 4. I am pretty doubtful that "Memory: 25kB" is going to be stable
>> enough for us to want that output memorialized in the regression ...
>
> Fair enough. I wanted to be a bit more sophisticated in my check than
> looking for a single value so I worked out something that distills the
> explain down to the key elements.

Works for me. While I'm sure this won't eclipse previous achievements
in this area, it still seems worthwhile. So committed with one minor
change to shorten a long-ish line.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2017-08-21 21:30:23 Re: Patch: Add --no-comments to skip COMMENTs with pg_dump
Previous Message Robert Haas 2017-08-21 18:43:04 Re: Proposal : For Auto-Prewarm.