| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Emre Hasegeli <emre(at)hasegeli(dot)com> |
| Cc: | Andreas Karlsson <andreas(at)proxel(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Subject: | Re: BRIN range operator class |
| Date: | 2015-05-12 19:54:24 |
| Message-ID: | 55525A70.2080103@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/12/2015 10:49 PM, Alvaro Herrera wrote:
> If in the future, for instance, we come up with a way to store the ipv4
> plus ipv6 info, we will want to change the page format. If we add a
> page version to the metapage, we can detect the change at pg_upgrade
> time and force a reindex of the index.
A version number in the metapage is a certainly a good idea. But we
already have that, don't we? :
> /* Metapage definitions */
> typedef struct BrinMetaPageData
> {
> uint32 brinMagic;
> uint32 brinVersion;
> BlockNumber pagesPerRange;
> BlockNumber lastRevmapPage;
> } BrinMetaPageData;
>
> #define BRIN_CURRENT_VERSION 1
> #define BRIN_META_MAGIC 0xA8109CFA
Did you have something else in mind?
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-05-12 20:02:36 | Re: BRIN range operator class |
| Previous Message | Alvaro Herrera | 2015-05-12 19:49:20 | Re: BRIN range operator class |