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 1sS0Vz-00355I-MP for pgsql-hackers@arkaria.postgresql.org; Thu, 11 Jul 2024 20:35:43 +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 1sS0Vw-000TvX-Tn for pgsql-hackers@arkaria.postgresql.org; Thu, 11 Jul 2024 20:35:40 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sS0Vw-000TvP-JX for pgsql-hackers@lists.postgresql.org; Thu, 11 Jul 2024 20:35:40 +0000 Received: from mail-lf1-x12a.google.com ([2a00:1450:4864:20::12a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sS0Vt-001ayL-V2 for pgsql-hackers@lists.postgresql.org; Thu, 11 Jul 2024 20:35:39 +0000 Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-52e9944764fso1417383e87.3 for ; Thu, 11 Jul 2024 13:35:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1720730135; x=1721334935; darn=lists.postgresql.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=b/aILfljppQlorImehaMTQZOPHVGCg8Jb+DAc2eF2fU=; b=OQq2aYuFyTIR3CrGewKWfAnbdxw4z2OaDaeOMqty4B1RSxFhRwxmsazh5Hgze8IJZL IuDGTYSwgNGyl5oNcgrviNdShucSc5mWc1pNaUI2ujQZd84+L76sv+rU4DqD1yooOUOh mKr/yLXF+za0iw4xa39UCT8zP9u3QcLMsQN/zzCpVXGv1mVed/HcPRrvE9KzvE2w9UXL a3BVEdVvFuBxJ1jHuq0P7we6P6xdY4nkNG7ldyEzT8tRwXHgcKTUvwtnmpVnx2LJ4BX/ mBuls6WAiE+RmF1LB14TZu8nAlW/aCAnqh8kRVTP1o3gp22gkdtvG3bXH1fum/sGHOgh rUQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720730135; x=1721334935; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=b/aILfljppQlorImehaMTQZOPHVGCg8Jb+DAc2eF2fU=; b=ZgPX5rhIDk13zmp4r69y9mRx/HLSqFGQpJWyYgk90uSQCuvD669ze/mSxY2pQGEts4 JTB3RrdRqCboUW/rqc8FnTSXWsacJFI3yKL1Gkzw6TRDELT0gwhHZ01cnFOOszTYCu/2 Y77dQ2HA+3jsSfmddzaLU3vDJy4O/0cEM/jNuLdqZWM5EHU6ifnF7JchqxWbLtV819+x jsxhHdZfbxwi0uF7hCEjXTsGa8AMjV+e1dSxRP4vBHHSUpwvJJJE4iRm87A6TKlt2WaR fw6Qjp5zn66WSI2SiywFIzxyvHRcOup5WfWsPyYlguAT7NlTfHcViwfO3Q38jAdliXYt yP3w== X-Forwarded-Encrypted: i=1; AJvYcCUJep1AGIcAdYWRuvDpYcxAO7C+SdJnYSrmKnQyjGpU09T/ziPPjBh/wMJyyswIU/sn7uX9TzZOBl0e2eyLf/HMH/IkhfPwHFXQX1ri38MThlMQ X-Gm-Message-State: AOJu0YwFFIP0uaCJd/uwPYQx2u84Z9fiFrzpysnTBSD+wFptG8lki2e9 Hw79laYkXTi+C9EgxdcuJ1it5LgWFm7hwAY0SBfrCueUjwqGxC5T X-Google-Smtp-Source: AGHT+IHjGemfVXakJxOzrlujHx1+LQ9NEoxqHmKO0iPbL0Ek4ObeAfUIWDIZcmpdOzUht2qFA/tYYQ== X-Received: by 2002:a05:6512:3d02:b0:52e:767a:ada3 with SMTP id 2adb3069b0e04-52eb99cb00dmr6660681e87.47.1720730135307; Thu, 11 Jul 2024 13:35:35 -0700 (PDT) Received: from smtpclient.apple ([2a01:4b00:c00c:a500:2883:d11e:486d:7b7]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4279f259761sm261595e9.11.2024.07.11.13.35.34 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Jul 2024 13:35:34 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\)) Subject: Re: CREATE INDEX CONCURRENTLY on partitioned index From: Ilya Gladyshev In-Reply-To: Date: Thu, 11 Jul 2024 21:35:24 +0100 Cc: Alexander Pyhalov , pgsql-hackers@lists.postgresql.org, Masahiko Sawada , Michael Paquier , =?utf-8?B?IuadjuadsCjmhY7ov70pIg==?= Content-Transfer-Encoding: quoted-printable Message-Id: <5F602655-58E6-4562-85D3-34E04BE9D60C@gmail.com> References: <37d3f0a984a15f6465b83027eed8c588@postgrespro.ru> <8fe0027c-a4f9-43a0-afc1-20362c159d07@gmail.com> <76a11eea-c5ae-4034-971d-c8a2df0bb14d@gmail.com> <55cfae76-2ffa-43ed-a7e7-901bffbebee4@gmail.com> To: Justin Pryzby X-Mailer: Apple Mail (2.3774.600.62) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk It is broken in master, I just didn=E2=80=99t want to create a separate = thread, but it can be fixed independently. As I remember, the problem is = that progress is tracked for each table in the hierarchy as if the table = is processed separately, without ever setting partitions_total and = partitions_done counters. > 11 =D0=B8=D1=8E=D0=BB=D1=8F 2024=E2=80=AF=D0=B3., =D0=B2 13:31, Justin = Pryzby =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0= =B0): >=20 > On Sat, Jun 15, 2024 at 07:56:38PM +0100, Ilya Gladyshev wrote: >> In addition, I noticed that progress tracking is once again broken = for >> partitioned tables, while looking at REINDEX implementation, = attaching the >> second patch to fix it. >=20 > Thanks for the fixes, I started reviewing them but need some more time > to digest. >=20 > Do you mean that progress reporting is broken in master, for REINDEX, = or > just with this patch ? >=20 > --=20 > Justin