Re: Hypothetical indexes using BRIN broken since pg10

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Julien Rouhaud <rjuju123(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Hypothetical indexes using BRIN broken since pg10
Date: 2019-11-21 01:33:22
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Nov 19, 2019 at 09:48:59PM +0900, Michael Paquier wrote:
> Re-reading the thread. Any design change should IMO just happen on
> master so as we don't take any risks with potential ABI breakages.
> Even if there is not much field demand for it, that's not worth the
> risk. Thinking harder, I don't actually quite see why it would be an
> issue to provide default stats for an hypothetical BRIN index based
> using the best estimations we can do down to 10 with the infra in
> place. Taking the case of hypopg, one finishes with an annoying
> "could not open relation with OID %u", which is not that nice from the
> user perspective. Let's wait a bit and see if others have more
> arguments to offer.

Okay. Hearing nothing, committed down to 10.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message TAKATSUKA Haruka 2019-11-21 01:42:57 Re: fix "Success" error messages
Previous Message Masahiko Sawada 2019-11-21 01:23:07 Re: [HACKERS] Block level parallel vacuum