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 1lomvF-0002ja-Ba for pgsql-docs@arkaria.postgresql.org; Thu, 03 Jun 2021 12:58:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lomvE-0003sY-58 for pgsql-docs@arkaria.postgresql.org; Thu, 03 Jun 2021 12:58:04 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lomvD-0003sD-N7 for pgsql-docs@lists.postgresql.org; Thu, 03 Jun 2021 12:58:03 +0000 Received: from mail-qv1-xf2e.google.com ([2607:f8b0:4864:20::f2e]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lomvB-0003It-Nf for pgsql-docs@postgresql.org; Thu, 03 Jun 2021 12:58:02 +0000 Received: by mail-qv1-xf2e.google.com with SMTP id e18so3077714qvm.10 for ; Thu, 03 Jun 2021 05:58:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hasegeli.com; s=google; h=mime-version:references:in-reply-to:reply-to:from:date:message-id :subject:to:cc; bh=8MhxNx4sRUK2kDv6fs66ytssanYKzCdrcq9DChnycM0=; b=ufEhc2CYlHxjf2SC4DRvC01cFbfMVv4ulN12tg4pczRQyfiIZhk4+2zOsL1fHZh2Tb AS+AZBh2mF8K8RjB19PGh7E6G1nOj4446ra97he46vOKzeWB2DmbngJ2E6s4zUoEIg6C oZAeAS5RJm3v6Wsx4ZTB9DFn4zQN+faxtFfIc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:reply-to :from:date:message-id:subject:to:cc; bh=8MhxNx4sRUK2kDv6fs66ytssanYKzCdrcq9DChnycM0=; b=RhVvZywMcEOPqAnIA51Kt2JjFsmOx4+ZlRvRH+QjpekEHJS8LykB68h3V55Xyrh0lm tpE7HRJLp673H15DWj6xPoEfipUIR+RfPj9OAZ4DvqZvIcei8ITHMoIWfHDAR85fj7Eg Uv0W3pzcmeXB5IvmgC3T+CQ3Efl6LzyaEGlyJLds5QZ3jiRA97bs2bAUL/1jaDnJf06b nMeGE8HHP/6ino96zRCyelAICsnwID8WzCAdUyaBU8remhVYI28YZfRxkQT9krdpEozm vSpqho9KDXvFBiYOWqakVoiKcLm9DeDs5rBRMJWhFGEjAcvvURG69ykge1hUitBvKk65 sIxA== X-Gm-Message-State: AOAM530OpzAkZhAEyupngo2VNk6sQNJ0yFwCWXb4AFICxmm7SWHLXqBm dsuLxUt9fNkx89tPrqt9jmz/Cq8yhWjU94D/ioHKHA== X-Google-Smtp-Source: ABdhPJzZz67xQShqhzMsnx1q6F2ut7CymhJgxnYR+OADhvYigWDLJYQB3yvyz9kOad71DkUkjiMbsQC6d9fYCO4mJpU= X-Received: by 2002:a05:6214:1233:: with SMTP id p19mr18639954qvv.39.1622725080619; Thu, 03 Jun 2021 05:58:00 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Reply-To: emre@hasegeli.com From: Emre Hasegeli Date: Thu, 3 Jun 2021 15:57:24 +0300 Message-ID: Subject: Re: Note that ALTER TABLE cannot alter generated stored columns To: Peter Eisentraut Cc: pgsql-docs@postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > I don't follow why you put this documentation under ALTER TABLE ... DROP > EXPRESSION. That action doesn't seem related to what you were hoping to do. I thought that's where it would be if we had ADD/SET EXPRESSION statements, just like the ADD/SET GENERATED statements just below.