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 1o5yvq-0003e6-TC for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Jun 2022 00:18:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o5yvp-0002Vb-7h for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Jun 2022 00:18:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o5yvo-0002VS-PX for pgsql-hackers@lists.postgresql.org; Tue, 28 Jun 2022 00:18:16 +0000 Received: from mail-qk1-x731.google.com ([2607:f8b0:4864:20::731]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o5yvj-0001Nn-Fq for pgsql-hackers@postgresql.org; Tue, 28 Jun 2022 00:18:16 +0000 Received: by mail-qk1-x731.google.com with SMTP id v6so8580284qkh.2 for ; Mon, 27 Jun 2022 17:18:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=1+b04cqWTLYhr7LCS9O3HV1VNySvVmCfq66Yl74D9Vc=; b=EnpQrQPMIIluQ1OOE5ZOrDgL275rVfqYqq9Wn1ZAW1wPcBsXe47AYWbV0uS3VGv/n8 e7W5bpmr+GjxW89ddkHzaPeC72MnoXNOswfA7lOKouIVqyx1uGEJz576sGOzjiB/DVLg 5gComhdYXF1Ur7s5tBGw0aWNTJIWuTBaSoyh9AOnUqO4F6kpDs4wJcmfzRh1CdYBS5Rv /15DPKj057YK2srF8McvzGAo7PTJ1WoFSlIMCMwQNsJqSL6FDu9gRNSYwzuJ4g8N4ELG JZOmvV95lWn0F8uiIf6Hzvt3bpixGW3eZ6+zR8/1GjhiDSZ+7A3utNgkN0mZB/Ejjf/J RtFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=1+b04cqWTLYhr7LCS9O3HV1VNySvVmCfq66Yl74D9Vc=; b=bpuWzo/JOAaJEbvXJKFWTzimTu96rcbV1+YSxEWUWWYkbAS0EzFFtASxChPb6bu4az Hmz+ZLq6j+2y5/9LWoEyYlKgAI+60wZDKY70dOswgn/XhWs9xB5+BIKQMcHY0LY/rt28 1g77EcXgud3u33Uajh2I8VTsN8ih2cee1W862xRedgLWhQCNaI0pP2hmGPE8dyRZlrxZ 7lur93+41l/wqp6LrMkuJZwYlFsxtIRrUzYqpmfhe1Bl28c/xNUbOkCR+dRpI4yB4YGu N4hixquqE27pUAfSoywsGAIspywFFghtzK3HN4WRMqLHv0rh8Tuh8oq0zmDvHOb1OsIK vMOw== X-Gm-Message-State: AJIora+qxyZiyKPeDXmKh2kZc1xjsDOB2K+qO543C9sR9DE/T2OTjIS8 BaFe8G3lFFQNWoHuCrZW2rTS1Q== X-Google-Smtp-Source: AGRyM1sUHB0QUZ7bp78vnhiWOJiOQsyDAwlVPSqUTomMTR+ulYeszZLk6ivK2FI55TUOVi9NuaypIw== X-Received: by 2002:a05:620a:13a3:b0:6af:a58:c139 with SMTP id m3-20020a05620a13a300b006af0a58c139mr9941854qki.751.1656375489573; Mon, 27 Jun 2022 17:18:09 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id f30-20020ac840de000000b00315110b47bcsm8035673qtm.22.2022.06.27.17.18.08 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Jun 2022 17:18:09 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id E52648006D0; Mon, 27 Jun 2022 19:18:07 -0500 (CDT) Date: Mon, 27 Jun 2022 19:18:07 -0500 From: Justin Pryzby To: Simon Riggs Cc: Ashutosh Bapat , Ashutosh Bapat , pgsql-hackers@postgresql.org Subject: Re: Allowing REINDEX to have an optional name Message-ID: <20220628001807.GF19662@telsasoft.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Maybe the answer is to 1) add a parenthesized option REINDEX(SYSTEM) (to allow the current behavior); and 2) make REINDEX DATABASE an alias which implies "SYSTEM false"; 3) prohibit REINDEX (SYSTEM true) SYSTEM, or consider removing "REINDEX SYSTEM;". That avoids the opaque and surprising behavior that "REINDEX DATABASE" skips system stuff but "REINDEX DATABASE foo" doesn't, while allowing the old behavior (disabled by default).