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 1l2ZCH-00014H-Jn for pgsql-novice@arkaria.postgresql.org; Thu, 21 Jan 2021 12:36:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l2ZCG-0004ld-Gj for pgsql-novice@arkaria.postgresql.org; Thu, 21 Jan 2021 12:36:20 +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 1l2ZCG-0004lW-7W for pgsql-novice@lists.postgresql.org; Thu, 21 Jan 2021 12:36:20 +0000 Received: from mail-ej1-x635.google.com ([2a00:1450:4864:20::635]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1l2ZCC-0004Kz-NX for pgsql-novice@lists.postgresql.org; Thu, 21 Jan 2021 12:36:19 +0000 Received: by mail-ej1-x635.google.com with SMTP id l9so2381141ejx.3 for ; Thu, 21 Jan 2021 04:36:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=lRw/kU+XFT+caFULjW/xINo4T2nH/C7TQuGYjRUHDLk=; b=NfAMFxsDwllhHf6g9o/Cq9kV1xDQNS1GYnOEExR4O7VYY6IBXf1/7hOUxwXDwQ72q7 IFytJNXGyaam7NfHcRa6zesGNVe/OiE/IUJ4/IsVBrYz5PPg5KQSpWgqp27CWDHr/ETA AsskmkR/ITM8gK04BLL+aFnKauFNLv2I4oH7LoRRXXsH6hal+/c/4EC/JOu3JD5AY4V8 a67D6JSI53a26m5y0zaFWaR2juxZR2Zv+ece0L7I9qP0O84SAVOATw1cMvOGXsT7bTxp 4F9m85bqngAP/nEWRLPGTubl6kn2a9Xa0JAqTMfYPxJ2dFZTf/WeS6IsWWISHn3z9kii bakA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=lRw/kU+XFT+caFULjW/xINo4T2nH/C7TQuGYjRUHDLk=; b=JIO576xhn0/p7Zx5/kS3PVj3QX2U5RVeHIdXTMB8hC+80c6J3vuDU//t13J1LNc+dh 9nubJOn4aCNLEtKE4BAvZDSlrJOYhgDb8JliBAEKMP3Kt1G+uQ7HyJ2l9/ogwsZC2FWt nO+uCRgq3kwiu0YzVWn8mv8Mtvqpl7L4y01RSpIINZVtUPczztLV/MMrkD2CqIWNXkdU joE6fgfqJrK/Wc3Jcs3fko0XFO6q7qENQRRV20k/6r3j+F8939aH4WgBZzNt9r3z8ysO DZ0KkWqSIILRf2hWVly9HZ4b6dlRhecXRuBabYBcb5YZXiKI54gbDfWSKQRZXQndmuWL NZCQ== X-Gm-Message-State: AOAM533N783/mobyuCeJh7Ca5aKlqEXvZ/C3nmL4gOExDct2st1TDT7s lkdc/UmAR/EXbeUuFAp2D/qZ1A== X-Google-Smtp-Source: ABdhPJwMCoNnPR+eM04NT+xtxHGWpY8Jon8tWrV9O5qxvlFmqD/gCRrO2/gn+f4XD7lJw1iLWA8Nkg== X-Received: by 2002:a17:907:d8e:: with SMTP id go14mr9296735ejc.472.1611232575796; Thu, 21 Jan 2021 04:36:15 -0800 (PST) Received: from localhost.localdomain (217-149-174-241.nat.highway.telekom.at. [217.149.174.241]) by smtp.gmail.com with ESMTPSA id j3sm2163016eja.2.2021.01.21.04.36.15 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 21 Jan 2021 04:36:15 -0800 (PST) Message-ID: <4c014c47efcfe56cd2aa708e592bd29d75bf4adf.camel@cybertec.at> Subject: Re: Postgres 12 - Generated Columns - Backup/Restore From: Laurenz Albe To: Santosh Udupi , pgsql-novice@lists.postgresql.org Date: Thu, 21 Jan 2021 13:36:14 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, 2021-01-20 at 17:32 -0800, Santosh Udupi wrote: > My Postgres 12 database tables have generated columns. I use pg_dump to backup > the database but when I restore using pg_restore, the generated columns are empty. > How do I trigger creating the data in the generated columns? Does the expression that generates the computed column uses an expression containing a function that is marked IMMUTABLE, but isn't really? Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com