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 1qwNSM-00BLkH-3n for pgsql-admin@arkaria.postgresql.org; Fri, 27 Oct 2023 14:04:58 +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 1qwNSK-00FqCs-7B for pgsql-admin@arkaria.postgresql.org; Fri, 27 Oct 2023 14:04:56 +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 1qwNSJ-00FqCk-Nd for pgsql-admin@lists.postgresql.org; Fri, 27 Oct 2023 14:04:55 +0000 Received: from mail-ed1-x530.google.com ([2a00:1450:4864:20::530]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qwNSG-002a5a-Us for pgsql-admin@lists.postgresql.org; Fri, 27 Oct 2023 14:04:54 +0000 Received: by mail-ed1-x530.google.com with SMTP id 4fb4d7f45d1cf-53e751aeb3cso3358182a12.2 for ; Fri, 27 Oct 2023 07:04:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20230601.gappssmtp.com; s=20230601; t=1698415491; x=1699020291; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=NnzLDYOor0EUy/Qr8bHxzsxO/cksH0R1FaOjQa97AdY=; b=n9Gvo8dM0kOXG+NUb8jTY0wdQIaQ9pkFZ+/6KhQOCD6b6K+8rRj8LWx5ld4ZlfNrh2 ewY0mL83aB1Av1a8Bn3kqQ+9YgXDjPjYMkDZhT+1GrF7o7+UeI7F34AYJdGEsVyQFusk nAs9HaVKWPu2r1vlyiT4u0B6f3RKrnkmvUG5pR4KbJ84MT9XZFw8UsnIgBpJiOCSmeVM 1A2yGQnCYbvmCjUBU0dFzQbPvC+p27Ej7VvbBXs5wNNv3RkNPUZhoNhth+1L0THlarZt XqSKZ5iAW+QjZdeoEYdLf5boNCSbF/ueIQtSl60qU+YnZ1a7kmAl6fMHAM9QFHREmPOS Bh8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698415491; x=1699020291; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=NnzLDYOor0EUy/Qr8bHxzsxO/cksH0R1FaOjQa97AdY=; b=MHZRAhdf2hlStsC35865VPlujPAceSwOOXoD7rd8fM2+FkOVMQXV9ftGjZmgqdmlA5 HXCF1ACL9IC7JLp0g01Lhz4krSsuJdyp/SNbJ8Ps4WaA/w9SQR5Lr6UNVJZYsWKsZWjS HN+q0UpJqpX/DYjdNHDsvxp0EBmsYaDyLtvF/KSpt6eSV5M5K+EU1urdwYjPsWB2lDFI ZcoO5vIj6dUHWulJVaP8ELBC7pyrKuPwOoIAMUUypzpPeSk2BcVcn/LJfPCf2m0f2Ogy snfb4OjYnKuk/ug1jNPsUdU4hVY4+5nLHzKH+bz+YMkaxlPcw0lN5GaZztipe7Uak5E/ FzHw== X-Gm-Message-State: AOJu0YyO6Z80GVL5gBVNsbIHw2iTjS4obB4Xga/c1SGR/X2VgFirqPsu Zsx7JoimozWKdV7ceWVwvE4PgvpeTvPcfncBJdY= X-Google-Smtp-Source: AGHT+IEgTmfzI8M9iV6VjjRDNcRv8cbizxPKVNgi209tIxVT0cFJptUYSsVHAfMyb0iP0Art2uJsww== X-Received: by 2002:a17:907:7ba1:b0:9bf:2ddf:1bca with SMTP id ne33-20020a1709077ba100b009bf2ddf1bcamr2566836ejc.62.1698415491216; Fri, 27 Oct 2023 07:04:51 -0700 (PDT) Received: from localhost.localdomain ([2001:871:5e:8321:e6fd:49be:4e52:be26]) by smtp.gmail.com with ESMTPSA id l17-20020a170906415100b009adc77fe165sm1235423ejk.118.2023.10.27.07.04.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 27 Oct 2023 07:04:50 -0700 (PDT) Message-ID: Subject: Re: Progress of ALTER TABLE on inheritance-partitioned table? From: Laurenz Albe To: Ron , pgsql-admin@lists.postgresql.org Date: Fri, 27 Oct 2023 16:04:50 +0200 In-Reply-To: <400b499f-7db5-4e00-ac1c-0b20e855dc88@gmail.com> References: <400b499f-7db5-4e00-ac1c-0b20e855dc88@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 2023-10-27 at 08:34 -0500, Ron wrote: > Pg 9.6.24 (Yes, I know; it's out of my control.) >=20 > I'm ALTERing that table to change a column from INTEGER to BIGINT. Of=20 > course, all of the partitions are pretty big. >=20 > Even though it's one giant transaction, is there any way for me to monito= r=20 > 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. Yours, Laurenz Albe