|From:||Jeff Davis <pgsql(at)j-davis(dot)com>|
|To:||Itagaki Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>|
|Cc:||Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: New VACUUM FULL|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Fri, 2009-11-13 at 10:47 +0900, Itagaki Takahiro wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> > BTW I think the vacstmt.options change, which seems a reasonable idea to
> > me, could be extracted from the patch and applied separately. That'd
> > reduce the size of the patch somewhat.
> It's a good idea. I separated the part into the attached patch.
> It replaces VacuumStmt's "vacuum", "full", "analyze", and "verbose"
> fields into one "options" flag field.
I added a separate commitfest item for this patch to track it separately
from the rewrite version of VACUUM:
> The only user-visible change is to support "VACUUM (options)" syntax:
> VACUUM ( FULL, FREEZE, VERBOSE, ANALYZE ) table (columns)
> We don't bother with the order of options in this form :)
I looked at this patch. You left INPLACE in the patch, which looks like
an oversight when you were separating the two. Please remove that from
> There is a debatable issue that we can use "VACUUM (VERBOSE) table (col)"
> in the abobe syntax. Columns are specified but no ANALYZE option there.
> An ANALYZE option is added automatically in the current implementation,
> but we should have thrown an syntax error in such case.
Sounds fine, but worth a mention in the documentation. Just add to the
"columns" part of the VACUUM page something like: "If specified, implies
Other than these two minor issues, I don't see any problems with the
patch. Please post an updated version to the new commitfest entry.
|Next Message||Tom Lane||2009-11-14 23:36:25||Re: patch - per-tablespace random_page_cost/seq_page_cost|
|Previous Message||Robert Haas||2009-11-14 22:56:27||Re: patch - per-tablespace random_page_cost/seq_page_cost|