| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Refactoring of heapam code. |
| Date: | 2016-08-05 13:30:49 |
| Message-ID: | CACjxUsPHCNvLtX=5yV+VCXO0UncV4fAZVg9HYbLSPTi2pSR7Hw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 5, 2016 at 2:54 AM, Anastasia Lubennikova
<a(dot)lubennikova(at)postgrespro(dot)ru> wrote:
> They can be logically separated into three categories:
> "primary storage" - r, S, t, v. They store data and visibility information.
> The only implementation is heapam.c
> "secondary index" - i. They store some data and pointers to primary storage.
> Various existing AMs and managed by AM API.
> "virtual relations" - c, f, m. They have no physical storage, only entries
> in caches and catalogs.
Materialized views (relkind == "m") have physical storage, and may have indexes.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2016-08-05 13:33:48 | Re: Cache Hash Index meta page. |
| Previous Message | Robert Haas | 2016-08-05 12:51:42 | Re: regression test for extended query protocol |