Re: pg_class.reltuples of brin indexes

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_class.reltuples of brin indexes
Date: 2018-03-27 14:28:03
Message-ID: 20180327142803.5tzvrkouc43arddc@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> writes:
> > I think number of index tuples makes sense, as long as that's what the
> > costing needs. That is, it's up to the index AM to define it. But it
> > clearly should not flap like this ...
>
> > And it's not just BRIN. This is what I get with a GIN index:
>
> Sounds like the same kind of thing we just fixed for SP-GiST :-(

Most likely I modelled the BRIN code after GIN.

--
Álvaro Herrera https://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 Yugo Nagata 2018-03-27 14:28:04 Re: [HACKERS] [PATCH] Lockable views
Previous Message Alvaro Herrera 2018-03-27 14:26:03 Re: XML/XPath issues: text/CDATA in XMLTABLE, XPath evaluated with wrong context