Re: Refactoring of heapam code. - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: Refactoring of heapam code.
Date
Msg-id CACjxUsPHCNvLtX=5yV+VCXO0UncV4fAZVg9HYbLSPTi2pSR7Hw@mail.gmail.com
Whole thread Raw
In response to Refactoring of heapam code.  (Anastasia Lubennikova <a.lubennikova@postgrespro.ru>)
Responses Re: Refactoring of heapam code.  (Anastasia Lubennikova <a.lubennikova@postgrespro.ru>)
List pgsql-hackers
On Fri, Aug 5, 2016 at 2:54 AM, Anastasia Lubennikova
<a.lubennikova@postgrespro.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: regression test for extended query protocol
Next
From: Amit Kapila
Date:
Subject: Re: Cache Hash Index meta page.