Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b2lho-0005ST-Ll for pgsql-hackers@arkaria.postgresql.org; Tue, 17 May 2016 20:35:04 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1b2lho-0003SB-2K for pgsql-hackers@arkaria.postgresql.org; Tue, 17 May 2016 20:35:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1b2lhl-0003NE-Ph for pgsql-hackers@postgresql.org; Tue, 17 May 2016 20:35:01 +0000 Received: from www.commandprompt.com ([2604:da00:2:2:5054:ff:fe07:7618] helo=lists.commandprompt.com) by magus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1b2lhg-0000wD-8U for pgsql-hackers@postgresql.org; Tue, 17 May 2016 20:35:00 +0000 Received: from [192.168.1.60] (spinlock.commandprompt.com [69.168.55.30]) by lists.commandprompt.com (Postfix) with ESMTPA id 0A45E613; Tue, 17 May 2016 13:34:51 -0700 (PDT) Received: from c-73-225-27-179.hsd1.wa.comcast.net ([73.225.27.179] helo=[192.168.1.60]) by assp.commandprompt.com with SMTPSA(TLSv1_2 ECDHE-RSA-AES128-GCM-SHA256) (2.4.5); 17 May 2016 13:34:51 -0700 Subject: Re: Reviewing freeze map code To: Alvaro Herrera , Masahiko Sawada References: <20160517193208.GA169606@alvherre.pgsql> Cc: Robert Haas , Ants Aasma , Stephen Frost , Andres Freund , "pgsql-hackers@postgresql.org" From: "Joshua D. Drake" Organization: Command Prompt, Inc. Message-ID: <573B806B.8020301@commandprompt.com> Date: Tue, 17 May 2016 13:34:51 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <20160517193208.GA169606@alvherre.pgsql> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Assp-Version: 2.4.5(15162) on assp.commandprompt.com X-Assp-ID: assp.commandprompt.com m1-17291-04911 X-Assp-Session: 7FA6DFEF49F8 (mail 1) X-Assp-Envelope-From: jd@commandprompt.com X-Assp-Intended-For: pgsql-hackers@postgresql.org X-Assp-Intended-For: andres@anarazel.de X-Assp-Intended-For: sfrost@snowman.net X-Assp-Intended-For: ants.aasma@eesti.ee X-Assp-Intended-For: robertmhaas@gmail.com X-Assp-Intended-For: sawada.mshk@gmail.com X-Assp-Intended-For: alvherre@2ndquadrant.com X-Assp-Original-Subject: Re: [HACKERS] Reviewing freeze map code X-Assp-Client-SSL: yes X-Pg-Spam-Score: -3.3 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org 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