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 1qwNgf-00BMQA-UG for pgsql-admin@arkaria.postgresql.org; Fri, 27 Oct 2023 14:19:45 +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 1qwNge-00G4UX-EO for pgsql-admin@arkaria.postgresql.org; Fri, 27 Oct 2023 14:19:44 +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 1qwNge-00G4UO-3N for pgsql-admin@lists.postgresql.org; Fri, 27 Oct 2023 14:19:44 +0000 Received: from mail-oa1-x2b.google.com ([2001:4860:4864:20::2b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qwNgb-0039j9-AD for pgsql-admin@lists.postgresql.org; Fri, 27 Oct 2023 14:19:43 +0000 Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-1dcfb2a3282so1301870fac.2 for ; Fri, 27 Oct 2023 07:19:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698416379; x=1699021179; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=xVWFMaXPoQ+VV4AqD9IQiV85MCyfyPAWBx802/2XHvY=; b=D0FNNTBdAxoBsl3Hq6ObtkRMlESkmCDxc0Qi6BIKHo9rAPd/KdRD8ratY9qYzDkpHw kvwNyTrq/JAAGTik5JhuHEeABlrBp3PM99RIdqHgKak8kQH0xdVyxC0x3rgv6Dmsm8LV 3epOTKYYvgny4ayLqDb1xNsFbHgOd6MIKCAH/DqbTgTvHqOJCL0QKuI7QaQWR2zADbYU EAljKkBkopp1VuqZswZpS06KmUHEarUARS10pCnYRjDVgC36nvBpwjK7eCcmLav3BRjh 4iGVmOBua8V9Ul5VjH0Du5XO3Q4TFwUXp6vx58OL4teK4QFQP5GT0l46Vd0eaATp+FTg XVEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698416379; x=1699021179; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=xVWFMaXPoQ+VV4AqD9IQiV85MCyfyPAWBx802/2XHvY=; b=p+eloGmz3Y61GyXB3eWwt5317+5gMYmkgv2j91PREH8enILg0dF3/LXetNjEsO6t4g J4AaXlBs49U0n6dLl/XcNwfa3UEcKzb5AviamxnA6lbdRzNguj9ADdiYs5J84Ah4POBM xCbyOxpz/IxtJZ8UVqRLGoc8EonZV67R8R86ww5xkWCDc3TE5xSTt8qFQnZtK95dHr+v x/VoqSBmj/XoT+0bgP9tENE7+hUA1fY4ddvFRiI8/UxUB3JODflrdQlERoU3bb9FnBZA +QTP+GxXl5gP4FOCP1+Jy33qUSPXt24RRMktmpjf2Xq72hJ1sWOGZ6teG5K3it0Mbla7 eZDA== X-Gm-Message-State: AOJu0Yz7314I2E+zM/fVcC3mVxU6sOZy84tR4T7rZJ03Gl1PnpZleML+ Ab7byegc7AF6HjyP29OyuXJrnKEbVAo= X-Google-Smtp-Source: AGHT+IGOLR+YzdeYb4PjummJBmQs02tkhGAkHe5WgFZl/C5yqcmuCW1N++fYF3O9T/rJkNe/9bW9Gg== X-Received: by 2002:a05:6871:b07:b0:1c8:39a6:779e with SMTP id fq7-20020a0568710b0700b001c839a6779emr3389907oab.19.1698416379099; Fri, 27 Oct 2023 07:19:39 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:e0e7:f6ad:239e:5da2? ([2600:1700:bd2c:b810:e0e7:f6ad:239e:5da2]) by smtp.googlemail.com with ESMTPSA id i191-20020a816dc8000000b005a8a78fa9d2sm741630ywc.17.2023.10.27.07.19.38 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 27 Oct 2023 07:19:38 -0700 (PDT) Message-ID: <19270938-47e4-4863-84e3-8f638eb357b3@gmail.com> Date: Fri, 27 Oct 2023 09:19:38 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Progress of ALTER TABLE on inheritance-partitioned table? Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: <400b499f-7db5-4e00-ac1c-0b20e855dc88@gmail.com> From: Ron In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/27/23 09:04, Laurenz Albe wrote: > On Fri, 2023-10-27 at 08:34 -0500, Ron wrote: >> Pg 9.6.24 (Yes, I know; it's out of my control.) >> >> I'm ALTERing that table to change a column from INTEGER to BIGINT. Of >> course, all of the partitions are pretty big. >> >> Even though it's one giant transaction, is there any way for me to monitor >> it's progress? > No, there is no way to monitor progress. The best you can do is to follow > the growth of the table on disk. > > You could consider logical replication ... oh, wait, 9.6. Since it's really a bunch of "small" partitions, can I track the (non)existence of those table oid files under $PGDATA/? -- Born in Arizona, moved to Babylonia.