pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Ants Aasma <ants.aasma@eesti.ee>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Reviewing freeze map code
Date: Tue, 17 May 2016 13:34:51 -0700
Message-ID: <573B806B.8020301@commandprompt.com> (raw)
In-Reply-To: <20160517193208.GA169606@alvherre.pgsql>
References: <20160517193208.GA169606@alvherre.pgsql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 05/17/2016 12:32 PM, Alvaro Herrera wrote:

>   Syntaxes are;
>   VACUUM (SCAN_ALL) table_name;
>   VACUUM (SCAN_ALL);  -- for all tables on database
>
> Is SCAN_ALL really the best we can do here?  The business of having an
> underscore in an option name has no precedent (other than
> CURRENT_DATABASE and the like).  How about COMPLETE, TOTAL, or WHOLE?
>

VACUUM (ANALYZE, VERBOSE, WHOLE)
....

That seems reasonable? I agree that SCAN_ALL doesn't fit. I am not 
trying to pull a left turn but is there a technical reason we don't just 
make FULL do this?

JD

-- 
Command Prompt, Inc.                  http://the.postgres.company/
                         +1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (256+ messages)  latest in thread

Message-ID: <573B806B.8020301@commandprompt.com>
Permalink:  ../573B806B.8020301@commandprompt.com/
Also on:    postgresql.org/message-id/573B806B.8020301@commandprompt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: jd@commandprompt.com, alvherre@2ndquadrant.com, sawada.mshk@gmail.com, robertmhaas@gmail.com, ants.aasma@eesti.ee, sfrost@snowman.net, andres@anarazel.de
  Subject: Re: Reviewing freeze map code
  In-Reply-To: <573B806B.8020301@commandprompt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox