Re: What to name the current heap after pluggable storage / what to rename?

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: What to name the current heap after pluggable storage / what to rename?
Date: 2018-12-19 19:35:44
Message-ID: BA69D3C1-6114-4F60-BF45-3E5C8AA4AA39@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 19 Dec 2018, at 20:21, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> I vote for calling the current heap "heap" - i.e. what the patchset is
> currently doing. As others have already noted, that's a perfectly
> good word for storing stuff in no particular order, and it's also a
> term with a very long history.

FWIW, +1

cheers ./daniel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-12-19 19:44:17 Re: lock level for DETACH PARTITION looks sketchy
Previous Message Robert Haas 2018-12-19 19:21:29 Re: What to name the current heap after pluggable storage / what to rename?