Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kD8OZ-0007at-Ng for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Sep 2020 15:40:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kD8OY-00025S-L6 for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Sep 2020 15:40:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kD8OY-00025J-BB for pgsql-hackers@lists.postgresql.org; Tue, 01 Sep 2020 15:40:26 +0000 Received: from mail-qk1-x742.google.com ([2607:f8b0:4864:20::742]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kD8OT-00011v-Uy for pgsql-hackers@lists.postgresql.org; Tue, 01 Sep 2020 15:40:24 +0000 Received: by mail-qk1-x742.google.com with SMTP id u3so1348791qkd.9 for ; Tue, 01 Sep 2020 08:40:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=Ls42NBcVYMCjnB69KZsGQZz175yFGxXmVObjayoToxM=; b=0Kvvf7ZlpHlSWuPjxjBN0I+bRFSAJY8HAoZU6lJSDX7a/maSbARmHYAmHUZhH2wO1r avwNh4rJh+cHVQPtETEAQaKNnjjrscuC3BRI1fScDy6gR/6wHSaKF6SLI1KcIsVA3hfb m+XXQ4S0YLChnXyEQ1ewpb+5BU7tq9gRQFCQVX1wInFRuFHdoHzR+jL+5Nbce4NtoSdg 7xUoAS4497lFswGw62I8wJYFJFUbPkUp/PQNP4Jij2lXdSR1j1VoHC3pmP9OrAYxnCZ2 sKWWRhs17G8kXhRR9RCj3PPdT0DIK/SZK6OaPlHDLgbRohMuFcXriAnm5CEVjBQ23n+q jfMw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=Ls42NBcVYMCjnB69KZsGQZz175yFGxXmVObjayoToxM=; b=TXzxMscZPAGNlJg8MvTOUILB/pHI49iKnQDYvLz60g9y+PqZwLsxDJfI9U64NsDqJs DnSAgVbbNuOEljSXf268VgZLT1krUSPqrZELeC+jbkF1/xoIJdXKYH+vho0ISH413plW HBlThYUmX65XMgrIn5WZGuj2DkENm7onfEI1t9+XA8ShsB1jpx1kS9+/kMEoc49LU+SH sYWljedM2uITbCMADDoJJvruvzDbJ+HbMsSYUQ5qGTsBTSLYx89BrIucYj9zUwBt6tHp ADttcGGiFBBsAx6BvitR4MoZM8orVNsddj0u3A7wageeSl/VVpVIYUQiLMYQx/Wt9INc aalw== X-Gm-Message-State: AOAM53016/qOyuTecCzt8PTW2QklumCt//HFtIw2bZxobiZCDLJ9kRaI Hc/ZfM93M2oDzMqIUApdKrfmqg== X-Google-Smtp-Source: ABdhPJzjed2R8rVTTdH+6dqXBw2Ut92ZOgaa3AwsSXaBf1NB1fnfTgwGqe+BAo5qd5xMuavgllvXyQ== X-Received: by 2002:a05:620a:74c:: with SMTP id i12mr2585966qki.438.1598974820906; Tue, 01 Sep 2020 08:40:20 -0700 (PDT) Received: from perhan.alvh.no-ip.org ([190.95.19.47]) by smtp.gmail.com with ESMTPSA id d9sm1909647qtg.51.2020.09.01.08.40.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 01 Sep 2020 08:40:19 -0700 (PDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 3563E2A1557; Tue, 1 Sep 2020 11:40:18 -0400 (-04) Date: Tue, 1 Sep 2020 11:40:18 -0400 From: Alvaro Herrera To: Justin Pryzby Cc: Michael Paquier , Alexey Kondratov , Masahiko Sawada , Steve Singer , pgsql-hackers@lists.postgresql.org, Robert Haas , Alexander Korotkov , Masahiko Sawada , Jose Luis Tallon Subject: Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly Message-ID: <20200901154018.GA7815@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20200811070922.GP20473@telsasoft.com> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-Aug-11, Justin Pryzby wrote: > On Tue, Aug 11, 2020 at 02:39:45PM +0900, Michael Paquier wrote: > > The grammar that has been committed was the one that for the most > > support, so we need to live with that. I wonder if we should simplify > > ReindexStmt and move the "concurrent" flag to be under "options", but > > that may not be worth the time spent on as long as we don't have > > CONCURRENTLY part of the parenthesized grammar. > > I think it's kind of a good idea, since the next patch does exactly that > (parenthesize (CONCURRENTLY)). > > I included that as a new 0002, but it doesn't save anything though, so maybe > it's not a win. The advantage of using a parenthesized option list is that you can add *further* options without making the new keywords reserved. Of course, we already reserve CONCURRENTLY and VERBOSE pretty severely, so there's no change. If you wanted REINDEX FLUFFY then it wouldn't work without making that at least type_func_name_keyword I think; but REINDEX (FLUFFY) would work just fine. And of course the new feature at hand can be implemented. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services