Re: [HACKERS] [doc fix] Really trivial fix for BRIN documentation - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject Re: [HACKERS] [doc fix] Really trivial fix for BRIN documentation
Date
Msg-id 0A3221C70F24FB45833433255569204D1F6A6269@G01JPEXMBYT05
Whole thread Raw
In response to Re: [HACKERS] [doc fix] Really trivial fix for BRIN documentation  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
From: Simon Riggs [mailto:simon@2ndquadrant.com]
> Pushed, but using "heap" rather than "table", for clarity. Thanks for the
> patch.

Thank you for responding so quickly.  I'm comfortable with "heap."  On the other hand, src/backend/access/brin/README
uses"table" as follows.  Second, I thought users would feel more familiar with the general term "table."  Third, I
supposedPostgreSQL might add support for other structures for tables than heap in the future, like SQL Server provides
heap(non-clustered table) and clustered tables.
 

At index creation time, the whole table is scanned; for each page range the
summarizing values of each indexed column and nulls bitmap are collected and
stored in the index.

I should have written the reason I chose "table."  Anyway, I'm OK with heap.

Regards
Takayuki Tsunakawa


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Bold itemized list entries
Next
From: Amit Langote
Date:
Subject: [HACKERS] foreign partition DDL regression tests