Re: a fast bloat measurement tool (was Re: Measuring relation free space)

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: a fast bloat measurement tool (was Re: Measuring relation free space)
Date: 2014-09-25 13:43:14
Message-ID: CA+U5nMLUvThqrCTmeruMWg9=2Z3HbLHATbJf427-83CpwOvh8g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 25 September 2014 10:41, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
> On 2014-09-25 10:24:39 +0530, Abhijit Menon-Sen wrote:
>> At 2014-09-24 11:09:24 +0200, andres(at)2ndquadrant(dot)com wrote:
>> > I think it's completely unacceptable to copy a visibility routine.
>>
>> OK. Which visibility routine should I use, and should I try to create a
>> variant that doesn't set hint bits?
>
> I've not yet followed your premise that you actually need one that
> doesn't set hint bits...

Not least because I'm trying to solve a similar problem on another
thread, so no need to make a special case here.

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-09-25 13:49:47 Re: missing isinf declaration on solaris
Previous Message Thom Brown 2014-09-25 13:42:04 Re: RLS Design