Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c4qtg-00031O-Ul for pgsql-docs@arkaria.postgresql.org; Thu, 10 Nov 2016 15:04:13 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1c4qtg-0000SL-8R for pgsql-docs@arkaria.postgresql.org; Thu, 10 Nov 2016 15:04:12 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c4qtf-0000MV-7Q for pgsql-docs@postgresql.org; Thu, 10 Nov 2016 15:04:11 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c4qtb-0007gP-RD for pgsql-docs@postgresql.org; Thu, 10 Nov 2016 15:04:09 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id uAAF462A005020; Thu, 10 Nov 2016 10:04:06 -0500 From: Tom Lane To: Euler Taveira cc: vodevsh@gmail.com, pgsql-docs@postgresql.org Subject: Re: misleading ALTER TABLE SET STORAGE In-reply-to: <271e1212-5159-f939-ed9c-10573a538f69@timbira.com.br> References: <20161108142739.27613.11510@wrigleys.postgresql.org> <271e1212-5159-f939-ed9c-10573a538f69@timbira.com.br> Comments: In-reply-to Euler Taveira message dated "Thu, 10 Nov 2016 11:46:34 -0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5018.1478790246.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Thu, 10 Nov 2016 10:04:06 -0500 Message-ID: <5019.1478790246@sss.pgh.pa.us> X-Pg-Spam-Score: -4.8 (----) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org Euler Taveira writes: > On 08-11-2016 11:27, vodevsh@gmail.com wrote: >> Was reading >> https://www.postgresql.org/docs/current/static/storage-toast.html and the >> bit with "...table column can be altered with ALTER TABLE SET STORA= GE..." >> appeared misleading to me. > AFAICS ALTER TABLE SET STORAGE means ALTER TABLE ... ALTER COLUMN SET > STORAGE. There is no ALTER TABLE SET STORAGE per table. It seems you are > confusing with ALTER TABLE SET (storage_parameter =3D value, ...). > Perhaps, we should use the complete command (ALTER TABLE tablename ALTER > COLUMN colname SET STORAGE storagetype) or link ALTER TABLE to avoid > confusion. Our usual practice is to insert ellipses where there are omissions, so this probably ought to read "ALTER TABLE ... SET STORAGE". We could go with "ALTER TABLE ... ALTER COLUMN ... SET STORAGE", but that's more verbose and not any more correct. A link might not be a bad thing either, but it's sort of an independent question. regards, tom lane --=20 Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs