Horton

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

Arkhena <arkhena@gmail.com>

View thread View on postgr.es
From: Arkhena <Arkhena@gmail.com>
To: peter.eisentraut@2ndquadrant.com
Cc: Andres Freund <andres@anarazel.de>, Pg Hackers <pgsql-hackers@postgresql.org>, kommi.haribabu@gmail.com, a.korotkov@postgrespro.ru, robertmhaas@gmail.com, amit.kapila16@gmail.com
Date: 2018-12-19T08:44:33Z
Lists: pgsql-hackers 
>
>
> I'm wondering where the choice of the name "heap" originally came from
> and what it refers to.


It seems to me that "heap" is an Oracle word (as explained here[1]).

> By default, a table is organized as a heap, which means that the database
places rows where they fit best rather than in a user-specified order.

[1]:
https://docs.oracle.com/en/database/oracle/oracle-database/18/tgsql/optimizer-access-paths.html#GUID-53905BCD-3EAD-4B44-8CCC-C442A80647E8


-- 
Adoptez l'éco-attitude
N'imprimez ce mail que si c'est vraiment nécessaire

Commits

  1. Replace heapam.h includes with {table, relation}.h where applicable.

  2. Replace uses of heap_open et al with the corresponding table_* function.

  3. Introduce access/{table.h, relation.h}, for generic functions from heapam.h.