Re: proposal: integration bloat tables (indexes) to core - Mailing list pgsql-hackers

From Tom Lane
Subject Re: proposal: integration bloat tables (indexes) to core
Date
Msg-id 25887.1465838204@sss.pgh.pa.us
Whole thread Raw
In response to Re: proposal: integration bloat tables (indexes) to core  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: proposal: integration bloat tables (indexes) to core  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Re: proposal: integration bloat tables (indexes) to core  (Thomas Kellerer <spam_eater@gmx.net>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Jun 13, 2016 at 3:23 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> There are lot of useful queries (views), that are on our wiki. Some queries
>> are necessary for maintenance, and I am thinking these queries should be
>> integrated part of Postgres.

> It's likely to be hard to get agreement on which things to include.
> But if we can, it might be worth doing.  It would be nice to do it as
> an extension.

The problem with an extension is: when we make a core change that breaks
one of these views, which we will, how can you pg_upgrade a database
with the extension installed?  There's no provision for upgrading an
extension concurrently with the core upgrade.  Maybe there should be,
but I'm unclear how we could make that work.

At the same time, I'm pretty suspicious of putting stuff like this in
core, because the expectations for cross-version compatibility go up
by orders of magnitude as soon as we do that.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Reviewing freeze map code
Next
From: Simon Riggs
Date:
Subject: Re: New design for FK-based join selectivity estimation