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 1sGxKf-001Nwb-IF for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Jun 2024 08:58:22 +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 1sGxKe-004FUG-5S for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Jun 2024 08:58:21 +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 1sGxKd-004FU8-SA for pgsql-hackers@lists.postgresql.org; Tue, 11 Jun 2024 08:58:20 +0000 Received: from mail-ej1-x62f.google.com ([2a00:1450:4864:20::62f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sGxKc-0014tK-OQ for pgsql-hackers@postgresql.org; Tue, 11 Jun 2024 08:58:20 +0000 Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-a6f0dc80ab9so100154466b.2 for ; Tue, 11 Jun 2024 01:58:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718096297; x=1718701097; 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=wSP3Yo8w2bpT/ksxCzmiyMCVODM7zDaRmVUh4JtZgrE=; b=CDaAPx92RTKKDd86h0i1X00LJB6HXVlrwiZOM7AyAQyxtHnW/PDnIieKx2Dh8VXbRJ CFPlPBuVySvMvCoGKtbv89gBfn0/nh+Tk5aRL9UNvDcDEOhc9Kt9/uvh9L7rLjmjuKQH IFjLoE1NJCLMjudOg/51T7TSSmoeYwhT9SpWCwnZF8qP0cdqYROVzBmp2X0mpdpM9Qa/ +4varO4CNWAT8IihYLFMU03WBn58NRuTmtDxKJPV5mXdhqSfrG996K2/5DM0k+3ZMFsy uB/koFeFRnuVwQfvtVtp6+d1Hd2hnfbqC75IJIv7I6ziRlRJcFNK9og5u7qv8GP+FRQG 8FPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718096297; x=1718701097; 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=wSP3Yo8w2bpT/ksxCzmiyMCVODM7zDaRmVUh4JtZgrE=; b=aGe2/cnVrBIdEs795FOUT/oR6L0b3khZOP4di3MOmByrolCVd/49w/9C0L0qnvGStc 4ZNA5SP4HWNmDvBQg8V9Ol8WTzvYPaHHDSmeFuxxlD8vIpkaWtLlUVD5N6PbZrcKUVoI RrMxV9Gv5WzNagUiz1t60g2GfQPtgzgrVVPy+c08QMUaP9J872zzMWbPt2DOWWADQMtB asl+sFPa48qZkkAxYuio8CfDWcRjUuQSsR78B2AtrxoLAm58931X8b3OfF/saGxkpnfB Ibl1ZrUDWnJVemBtbmuyH5InE5dlnZr3NdC4Rpfhtv0bCuNqhhog0ZHX3B9YTJOAgXYH DUug== X-Forwarded-Encrypted: i=1; AJvYcCUv5hMHvnSbvx8h7HwKL5PiIJJtXnJGUXoFtIuKOi+Ct35oaNEDGF957HKDH/f2GVUpXujUQfANbLh8BGRDob1FYNndnxhpb+BeH00+ X-Gm-Message-State: AOJu0YzrN3EgpdSef4bLMJHBbWTuu/Fkwno3cy6+tbqmkQGLXunTwAHs wpyB809FeVcaalWZBe51KWbphSlCon2gGNs3TwlJLprpzEyuB445IMHQRDnK0FHXo+8a4JPWNio P5R99i0hHRN6+ymVPhmCg7ttpHSY= X-Google-Smtp-Source: AGHT+IGNjdH5Cg0HWhF9C+bHVXZ9T8VPYt+bXRIYs2ZtNcHg/Upwl/XeariNZpB2QGJD0RHWe5LKgcFi6yyaoROo9WQ= X-Received: by 2002:a17:906:7c4:b0:a6e:e4dd:d8b9 with SMTP id a640c23a62f3a-a6ee4ed1b59mr597731066b.46.1718096297172; Tue, 11 Jun 2024 01:58:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Michail Nikolaev Date: Tue, 11 Jun 2024 10:58:05 +0200 Message-ID: Subject: Re: Revisiting {CREATE INDEX, REINDEX} CONCURRENTLY improvements To: Matthias van de Meent Cc: Melanie Plageman , PostgreSQL Hackers , Andrey Borodin Content-Type: multipart/alternative; boundary="0000000000007ba72e061a9977d5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007ba72e061a9977d5 Content-Type: text/plain; charset="UTF-8" Hello. I did the POC (1) of the method described in the previous email, and it looks promising. It doesn't block the VACUUM, indexes are built about 30% faster (22 mins vs 15 mins). Additional index is lightweight and does not produce any WAL. I'll continue the more stress testing for a while. Also, I need to restructure the commits (my path was no direct) into some meaningful and reviewable patches. [1] https://github.com/postgres/postgres/compare/master...michail-nikolaev:postgres:new_index_concurrently_approach --0000000000007ba72e061a9977d5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello.

I did the POC=C2=A0(1) of the me= thod described in the previous email, and it looks promising.
It doesn't block=C2=A0the VACUUM, indexes are built=C2=A0ab= out 30% faster (22=C2=A0mins=C2=A0vs 15=C2=A0mins). Additional index is lig= htweight and does not produce any WAL.

I'll co= ntinue the more stress testing for a while. Also, I need to restructure the= commits (my path was no direct) into some meaningful=C2=A0and reviewable p= atches.

--0000000000007ba72e061a9977d5--