Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nEvOM-0004o1-1X for pgsql-admin@arkaria.postgresql.org; Tue, 01 Feb 2022 15:48:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nEvOK-0003K6-UG for pgsql-admin@arkaria.postgresql.org; Tue, 01 Feb 2022 15:48:24 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nEvOK-0003Jx-GH for pgsql-admin@lists.postgresql.org; Tue, 01 Feb 2022 15:48:24 +0000 Received: from mail-wm1-x32b.google.com ([2a00:1450:4864:20::32b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nEvOH-0002l8-JF for pgsql-admin@lists.postgresql.org; Tue, 01 Feb 2022 15:48:24 +0000 Received: by mail-wm1-x32b.google.com with SMTP id c192so13042135wma.4 for ; Tue, 01 Feb 2022 07:48:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=5AoynxUKEtSFyuc/x4L5l7vI0bcMN2FHmuVqEONJoBs=; b=IBpZN40P2Gg1otqgCnyZiSaDTNOTU7k1c98Dna3MEYo4BUvzcpUpbBU1FzsxpUTMAx ybYTiTrQt91tIIUsRU5nt8J5AYWEwFqYrIxtdR/u7gdbYNVOEXcgap0tnoVRYZM0Siqn o7EhZJTZFvLeJ05hM6t58ENjrxHjrtNNmg0O05K9FIdQml1YL6Sp1qot15me2mHKehQ8 petev6nmV28Z5lHSaq9alGTSV6I1kWrA8ZtHAzxYhTx22FQsh2+NXsmtbaZGV4/L3xMr HfF4T2qo+c1aqMXbTA9yEBQPykq0tmlF4PnzeAQ2gOvdslu81HMkJGVnf1XUoCp5c7AR 5LzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=5AoynxUKEtSFyuc/x4L5l7vI0bcMN2FHmuVqEONJoBs=; b=29QMzZRmKz/2GwueqEYahV7vPbuK7PaCXdJfEE+5Casv4BMlktko9xw5GIf58npkhR xJAP+N8ilonj1vsOu+H8sA+QYCoQeppsQNxPVMFFNeRbjXDS4ACpN+gP+iM8O/iiKCAo x1vZzE5yKqJmY8ImAO4BzyLeXQQblK6ScKGpxGocWmx0wI8Guimq2gN5E/dhmkZBZqBy IrI9EtYGjAyd9t1TigvN8a/KryYDiA4I2Yi2qvqtiJcfskOKMG5cwwFsyD118Du7KjYS mUrw95KBt9zlzu4CfFDSNZU0AJNnSTu2e6BJqivZeRJdj74sntQcYSbJ79oEePZGdZUp LC6g== X-Gm-Message-State: AOAM5321AilgoSNLfJJbjoQjACbFLt9Ch3NkuADKe/aw3B4BuICz5VV2 WjbHHGTmjPj+70EdTRWV/S+1EQ== X-Google-Smtp-Source: ABdhPJznbwhOcMwx/Nhhh3DWEA/vhIToGtggS8QBY9346gFgB4IMIqIsS5N30eVrDy6tjeyCWzTguA== X-Received: by 2002:a05:600c:4e16:: with SMTP id b22mr2303680wmq.8.1643730499794; Tue, 01 Feb 2022 07:48:19 -0800 (PST) Received: from localhost.localdomain ([2001:871:5e:9b76:6826:232b:b8d9:8c47]) by smtp.gmail.com with ESMTPSA id m5sm2495082wms.4.2022.02.01.07.48.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 01 Feb 2022 07:48:19 -0800 (PST) Message-ID: <7e369505dedaa40dc14d3f8a944e1e9fb5ea0b76.camel@cybertec.at> Subject: Re: Determine potential change in table size after a column dropped? From: Laurenz Albe To: Jiankang Ji Cc: Wells Oliver , Ron , pgsql-admin@lists.postgresql.org Date: Tue, 01 Feb 2022 16:48:18 +0100 In-Reply-To: References: <84b61f419a0a5ba1049c7d74a85b6790bfe9e1e9.camel@cybertec.at> <599f850b109d98148ee512890ebe6ec4bfbfe26b.camel@cybertec.at> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.40.4 (3.40.4-2.fc34) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Tue, 2022-02-01 at 14:46 +0100, Jiankang Ji wrote: > I'm new in pgsql and have a similar problem for a timescale pgDB. > > [...] > > My question is: > 1. How to setup a watch-dog to detect [...] This is not similar at all. Don't hijack other threads. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com