Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rci59-001cIU-7Q for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Feb 2024 08:35:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rci57-003nAd-EH for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Feb 2024 08:35:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rci57-003nAU-4U for pgsql-hackers@lists.postgresql.org; Wed, 21 Feb 2024 08:35:57 +0000 Received: from mail-ej1-x635.google.com ([2a00:1450:4864:20::635]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rci55-0008px-8f for pgsql-hackers@postgresql.org; Wed, 21 Feb 2024 08:35:57 +0000 Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-a3f3d0d2787so43146866b.3 for ; Wed, 21 Feb 2024 00:35:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708504554; x=1709109354; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=oHDQnOxOlFc5+3A/E0Ojr8hzJ50HpGpPepV7ZaahXhk=; b=DdgXZUWVt7JXiCnxN8a2ElhPxc1kk9Cun10XB93zr/hVRAtp7v/k2uqsJxjIwgErZA 2aKs3e++LE3pfM1mUidFbIqbrgKtSax6OP3pj2OetchTQrfB+EHMe388gVptm9Z2gyZL w2CR4Nh1D8HywFog8x2a3w92ulr94MrCWTpoCFQL60T5GfJMfG2dIgNRQQTqir7JNNxB lvbeezyRqkm9LetBrJXvJZC7XbyU6TQFpR0h1hs9qM50BMixM7VE2afLcKdKTXbhK6gS yitsfSaj8xH4lDMvII+7F1r7H5qnI306MtjmAQ5giFiIVF/S0TbkkdnpZ+wMHVR4izy2 WS6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708504554; x=1709109354; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oHDQnOxOlFc5+3A/E0Ojr8hzJ50HpGpPepV7ZaahXhk=; b=D3Jys5o2CfQJ0ii6tKVARnYlfHcRB6qgKa9aqiUmRDVDIGcB1k974kOihZjwFVJrXg 1N7nPfuYTK7v8+hB+F2N0etW58AFjOvWSQRj/BaUfy20za3WJIqA7jcVl763aQHbrEcV 0LqQTqZpCWbZ68AEx7B06vKOpSRrMnhv9Ri384SNNp6VOCUJ46nrEQOtvRyK/06VeSR9 G3yJvnejHoNvIAVKlFpJvISX12zCPcRE8EFySwxYTwuWb2nxza2n5cJ/eXaIg5qdv3AD 1PhAZzG7tM/M3vKvTf5nBn6bjM78Qpz3FM+HdYRVrAPFOxHU99OwF/drqVZWTTNEBqtA xWKA== X-Forwarded-Encrypted: i=1; AJvYcCWQNEZSVtsrqqBdmnheAmRcv7QpZnHAlKvDwu/75jsEHVb6FV0ZVSGMTtCooA/rQJySo4tMSFbS/5iXZHQoaQsOXEsfN5LQQmfCmvfb X-Gm-Message-State: AOJu0Yx6X2TyMR3AcnRMbQcqhdjcMZ8LqfxLA6KSAgDjRise4veHgZ+E 9rtwGDLIVq51WtBMB0UXmJvZ2EAeX3gkz2xffmiu30HW5piDAjC+D9/Y1vIrk/cvCEVnQVrYV7V w3i/e3OlKML2ZaWN9Ujiv9aC3NPo= X-Google-Smtp-Source: AGHT+IHX7Q8eYQPDVzKfr6s1zefDeXDX3cv5dxYJUyyIjITv51WZlhp0+Qskcc/M4wo7seWngE84CTRgRvscYd0CGt4= X-Received: by 2002:a17:906:b796:b0:a3f:33c5:ffb5 with SMTP id dt22-20020a170906b79600b00a3f33c5ffb5mr763955ejb.76.1708504553759; Wed, 21 Feb 2024 00:35:53 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Michail Nikolaev Date: Wed, 21 Feb 2024 09:35:40 +0100 Message-ID: Subject: Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements To: Matthias van de Meent Cc: Melanie Plageman , PostgreSQL Hackers , Alvaro Herrera Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk One more idea - is just forbid HOT prune while the second phase is running. It is not possible anyway currently because of snapshot held. Possible enhancements: * we may apply restriction only to particular tables * we may apply restrictions only to part of the tables (not yet scanned by R/CICs). Yes, it is not an elegant solution, limited, not reliable in terms of architecture, but a simple one.