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 1mcz5Z-0006nr-CA for pgsql-admin@arkaria.postgresql.org; Wed, 20 Oct 2021 00:04:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mcz5V-0004xB-EX for pgsql-admin@arkaria.postgresql.org; Wed, 20 Oct 2021 00:04:09 +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 1mcz5V-0004x2-1W for pgsql-admin@lists.postgresql.org; Wed, 20 Oct 2021 00:04:09 +0000 Received: from mail-qt1-x82b.google.com ([2607:f8b0:4864:20::82b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mcz5S-0000gU-Bn for pgsql-admin@lists.postgresql.org; Wed, 20 Oct 2021 00:04:08 +0000 Received: by mail-qt1-x82b.google.com with SMTP id i1so1571896qtr.6 for ; Tue, 19 Oct 2021 17:04:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=XdefycD5UVmvsGAA0Yl9cEfQKF5R1fChpthwQWEN8qY=; b=N+PsKY/ol3xId1PtPcAxTIfoopoyrS0s3FibiHLul71tto/VLDGrwVdx1UOao3ftHp 7Zbs3HAHHYduK0pMcYlwgFjdhwvd7cQOQBhvutyIm/JqXBJ1FlLAiPhmq8EAyN7Y4JzU /gPMGRoDsw6ZbbVmgfkeOCkeGilao/ORYpO7nOPnDDN/dpnD20j1Xw7p1TBkDykDi4X7 eVupXAsn3QU/SGBwRUtYm1MxyQd7//NdKsTAciDP9hpMJp9TZz6VBZ4jALM7SC2hcgLO V17KKfAf6muUGllx64jLeuGVn0F9U+kvTjY5bs87JF+yrP4pMjJcbSDk+xfnTZj6Opd9 VsSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=XdefycD5UVmvsGAA0Yl9cEfQKF5R1fChpthwQWEN8qY=; b=fZu08bnP6nowq4tYRTE9LqXFv4/JLrY/yAGcIoMrbwIfoYG93K3VFtnLRX+KOciIE0 rxKGFnGDTjNhakLzYCM+2SfRGkkCYVlqme3hw3tcDrjrrtbn0XijDPgKj1izlt6aPeEJ ef4mjYOk4Dm8ud87MrK90MOB99QgaWbynEoji1PZxhh1zdb7t/pbZhIPdR1ZXs7gSKl9 lox7AZvK4SI5LNUZtmzE3GnhqWYetz0v+Yw4POm5J4CYEMJqsJmCXTS0y6JFL/NbGc/e Djn+1coBATC1lArWu3j8grvVW2nwf0xarLSSATVwwYtCrkCffTkq7+BW0YeMDbQ9P+xe Gqcw== X-Gm-Message-State: AOAM530S4vUyTZVMHq8kO2qs928Aof8NGIJlZzYB/LzHz52Yx1v/5UZY phPpwum76nsz6zcR+/55KOJfZYYACKHVGA== X-Google-Smtp-Source: ABdhPJxDPt0Epy7lYoVPbLy+p+D7dR4rYhdsA8VuArc1MLCb4fBIjZd97wFxPj1o4xTDZ+CyPSo3Lg== X-Received: by 2002:ac8:1e95:: with SMTP id c21mr3433137qtm.412.1634688243626; Tue, 19 Oct 2021 17:04:03 -0700 (PDT) Received: from [192.168.2.100] (pool-72-79-19-93.nwrknj.east.verizon.net. [72.79.19.93]) by smtp.gmail.com with ESMTPSA id o5sm251206qtg.24.2021.10.19.17.04.03 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Oct 2021 17:04:03 -0700 (PDT) Message-ID: <0d9bf8bf-d33d-f821-29a3-a890802731f2@gmail.com> Date: Tue, 19 Oct 2021 20:04:02 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Subject: Re: Renaming 800GB size table in postgresql Content-Language: en-US To: pgsql-admin@lists.postgresql.org References: From: Mladen Gogala 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/19/21 13:17, Vijaykumar Jain wrote: > so, if I read it correctly, the renaming operation is independent of > the size of the table (as it is just updating the system catalog > somewhere). Rename table is done in the data dictionary, where the table is defined. You don't even touch the table during the process. Regards -- Mladen Gogala Database Consultant Tel: (347) 321-1217 https://dbwhisperer.wordpress.com