Re: issue log message to suggest VACUUM FULL if a table is nearly empty

From: Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "Wang, Jing" <jingw(at)fast(dot)au(dot)fujitsu(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: issue log message to suggest VACUUM FULL if a table is nearly empty
Date: 2014-07-14 10:11:15
Message-ID: 20140714101115.GA21584@toroid.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi.

Do we have any consensus on this patch?

I took a quick look at it because no review was posted. The patch itself
does what it claims to, but from the discussion it doesn't seem like we
want the feature; or perhaps we only don't want it in its present form.

So which is more appropriate, returned with feedback or rejected?

(In the latter case, the TODO item should also be removed.)

-- Abhijit

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Abhijit Menon-Sen 2014-07-14 10:20:30 Re: pg_shmem_allocations view
Previous Message Shigeru Hanada 2014-07-14 10:07:59 Re: [v9.5] Custom Plan API