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 1loSMk-0003oO-3Z for pgsql-docs@arkaria.postgresql.org; Wed, 02 Jun 2021 15:01:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1loSMi-0004UZ-UK for pgsql-docs@arkaria.postgresql.org; Wed, 02 Jun 2021 15:01:04 +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 1loSMi-0004UJ-Nr for pgsql-docs@lists.postgresql.org; Wed, 02 Jun 2021 15:01:04 +0000 Received: from wforward2-smtp.messagingengine.com ([64.147.123.31]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1loSMe-0000WA-63 for pgsql-docs@postgresql.org; Wed, 02 Jun 2021 15:01:03 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailforward.west.internal (Postfix) with ESMTP id 5EDB71190; Wed, 2 Jun 2021 11:00:57 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Wed, 02 Jun 2021 11:00:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=usbEZSUsAj88vq2R7Lwdf6qYC404HAr6rytFHu2CR I4=; b=ucG70ppCRdqOdBDxMTLsBoiyeV1LsGBNW6vGOyJUf7GBlAcqVQ52bL+o7 4AhoaUL3WYOApE/F4x8px+QREMT3tz7O7n0rAVhvxILD+yXAKeIrbYxcBfyMBe4e sOB1rkFlwfNnjcDByO4GrF9vWkgJC599Mz6hRXrrlm4yYcgBPSkix2f6su++gVrn VRWRrvG1hErL6Wsibprg1PFInyRZdaeZAG6pFMSBE7O01DigwKBhX69ZkAalSJd/ 0/xq3RlflJPE8ZQisaqhNPGNb98Joe7Dx9TtVgbFFsD2YH8gzBlSpnZMfIWw90Eo RSfCdo9Fpj4mDrzaFblpk+GxCTOhw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrvdeljedgkeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhffkffgfgggjtgfgsehtje ertddtfeejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvghtvghr rdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhmqeenucggtffrrg htthgvrhhnpeelveehheeuieduieetiedtkeeuteelfeetjeffieffudegvdffvdfftdei vdeukeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 2 Jun 2021 11:00:55 -0400 (EDT) Subject: Re: Note that ALTER TABLE cannot alter generated stored columns To: emre@hasegeli.com, pgsql-docs@postgresql.org References: From: Peter Eisentraut Message-ID: Date: Wed, 2 Jun 2021 17:00:54 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 30.05.21 15:25, Emre Hasegeli wrote: > I was trying to change the generation expression of a generated stored > column using ALTER TABLE. It took me a while before I figured SET > GENERATED applies only to generated identity columns. I think it'd be > useful to note this in the documentation with something like the > attached. 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.