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

From Vik Fearing
Subject Re: proposal: integration bloat tables (indexes) to core
Date
Msg-id 57630C86.6020403@2ndquadrant.fr
Whole thread Raw
In response to Re: proposal: integration bloat tables (indexes) to core  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On 16/06/16 20:31, Jim Nasby wrote:
> On 6/13/16 12:16 PM, Tom Lane wrote:
>> 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.
> 
> On a first go-round, I don't think we should add entire views, but
> rather functions that serve specific purposes. For table bloat that
> means a function that returns what the heap size should be based on
> pg_stats. For locking, it means providing information about which PID is
> blocking which PID. After that, most everything else is just window
> dressing.

We already have that second one: pg_blocking_pids(integer)
-- 
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support



pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: proposal: integration bloat tables (indexes) to core
Next
From: Tom Lane
Date:
Subject: Parallelized polymorphic aggs, and aggtype vs aggoutputtype