Re: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)heroku(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates
Date: 2015-12-22 22:59:22
Message-ID: CA+TgmoYQ8v2-SPHcxfM+4fuO2+rtemjGssW7jRTyK1D7dRy7rA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 22, 2015 at 12:31 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mon, Dec 21, 2015 at 2:55 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> On Mon, Dec 21, 2015 at 10:53 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>> PFA my proposal for comment changes for 9.5 and master. This is based
>>> on your 0001, but I edited somewhat. Please let me know your
>>> thoughts. I am not willing to go further and rearrange actual code in
>>> 9.5 at this point; it just isn't necessary.
>>
>> Fine by me. But this revision hasn't made the important point at all
>> -- which is that 0002 is safe. That's a stronger guarantee than the
>> abbreviated key representation being pass-by-value.
>
> Right. I don't think that we should back-patch that stuff into 9.5.

OK, so I've gone ahead and committed and back-patched that. Can you
please rebase and repost the remainder as a 9.6 proposal?

Thanks,

--
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 Peter Geoghegan 2015-12-22 23:10:29 Re: A Typo in regress/sql/privileges.sql
Previous Message Robert Haas 2015-12-22 22:58:52 Re: A Typo in regress/sql/privileges.sql