Re: Freeze avoidance of very large table.

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Freeze avoidance of very large table.
Date: 2015-07-10 09:46:09
Message-ID: CANP8+jLYnm+yXCEoCUOF0MTU4h8tNv-y-ZiZNg1LytBhL=LjSQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10 July 2015 at 09:49, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> wrote:

>
> > It is a minor thing, but if there is no other use for this fourth
> > "bit-space", it seems a shame to waste it when there is some use for
> it. I
> > haven't looked at the code around this area to know how hard it would be
> to
> > implement the setting and clearing of the bit.
>
> I think so too, we would be able to use unused fourth status of bits
> efficiently.
> Should I include these improvement into this patch?
> This topic should be discussed on another thread after this feature is
> committed, I think.
>

The impossible state acts as a diagnostic check for us to ensure the bitmap
is not itself corrupt.

-1 for using it for another purpose.

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2015-07-10 10:13:04 Re: Fillfactor for GIN indexes
Previous Message Etsuro Fujita 2015-07-10 09:40:51 Minor code improvements to create_foreignscan_plan/ExecInitForeignScan