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

From: Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, 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: Re: issue log message to suggest VACUUM FULL if a table is nearly empty
Date: 2014-07-14 12:09:56
Message-ID: 20140714120956.GG325@toroid.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 2014-07-14 07:55:34 -0400, tgl(at)sss(dot)pgh(dot)pa(dot)us wrote:
>
> I'd vote for rejecting and annotating the TODO item with a link to
> this thread.

I've marked the patch as rejected and edited the TODO list to remove the
"easy". There was already a link to this thread there.

Thank you.

-- Abhijit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kohei KaiGai 2014-07-14 13:18:03 Re: [v9.5] Custom Plan API
Previous Message Fujii Masao 2014-07-14 12:01:34 Re: No exact/lossy block information in EXPLAIN ANALYZE for a bitmap heap scan