Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fQhei-0006dJ-2q for pgsql-admin@arkaria.postgresql.org; Wed, 06 Jun 2018 23:15:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fQheg-0001Yg-DM for pgsql-admin@arkaria.postgresql.org; Wed, 06 Jun 2018 23:15:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fQheg-0001YX-3Z for pgsql-admin@lists.postgresql.org; Wed, 06 Jun 2018 23:15:50 +0000 Received: from mail-ot0-x242.google.com ([2607:f8b0:4003:c0f::242]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fQhed-00082k-8Q for pgsql-admin@lists.postgresql.org; Wed, 06 Jun 2018 23:15:49 +0000 Received: by mail-ot0-x242.google.com with SMTP id l15-v6so8287944oth.6 for ; Wed, 06 Jun 2018 16:15:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=GVRPzQxTq6hdifks3ouF1DL/oWiTe4wvVP9k/sR6e5M=; b=kXXGlWSjVDxPtBNzI/nq9jB6GiOcEKOAhdihIhBU7HNLZzHbKe1/kLyV8oDog3mjo1 9ti3+kAeFEVHgo8BXFIHH3HfoB6iUjNucS7irG3FlroorGLI96OccmmXSx6+YTE0t2vG 6iAHciTZEIeabIRTowve/ukD8lheG4GsUM2g7fP1ubk4k8vwD2Oa/c6h0+SAiNq9GyHq vC2EVIfu6axLuGnAYwIfWow57dCjC/wvCtlPQ0Qg++RLgc7nEJz1IORFHuAOjHps4mWx /G9N6IwG7uvPm0XnTxiLArrTMf0wO2gfSz+ujd/g15lQQ39GJIo3+mtWheTHSDGI0I4g 4ywA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=GVRPzQxTq6hdifks3ouF1DL/oWiTe4wvVP9k/sR6e5M=; b=Z4uaDFJpyDUbzM1kiKXyDmw2kbocRvX5ST+JG0RUcWWFCovIfyV8o34/ilBFx7z7Rd aKkXsRlcX3rlm3KGRcTBylUtIjsA5BIWZKVthfA+744HDr0WV6o9FQ9DRLHD3HWigJDj AMr1eIfgDMkA4/QWvPRhAdW9njNrrbuEJQs1g1se3X7k9dib8edaJzKq15rOiOPoUqE/ agK1yRAy+Gv6D+8fBEK6as2r/HMdogTd1NmJLpn08ko6kO5FGH1aQEvcZF36pfUNgkWu PLdyEqsmgJZ/9LMLrKhxin4V7xZyBQHFU8tzM3qs6xkK58VYeFsskcUcQ9qp+c8mqFXj P3JQ== X-Gm-Message-State: APt69E2Era0/4C/PC+25+8WRy5xMBi10xeejvtJ+veehih434bwVF12C Y8RDonTdh7kofolEb/TSIZfxpg== X-Google-Smtp-Source: ADUXVKJIb/QTpcyDl/bJ7eeyC+cz1Ft1xy+PE931yKky0tN/L+Tvk4rryvfA5hZZAJ0ek62x1aBXjA== X-Received: by 2002:a9d:4e12:: with SMTP id p18-v6mr3439887otf.260.1528326944614; Wed, 06 Jun 2018 16:15:44 -0700 (PDT) Received: from [192.168.1.10] (ip70-171-116-89.no.no.cox.net. [70.171.116.89]) by smtp.googlemail.com with ESMTPSA id t15-v6sm5803022ott.6.2018.06.06.16.15.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 06 Jun 2018 16:15:43 -0700 (PDT) Subject: Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit To: pgsql-admin@lists.postgresql.org References: <3C61E858-5CA7-405D-B32A-B4C89D1AC62E@elevated-dev.com> <05FBE51B-5256-4756-8AE2-98850D3163AF@ciena.com> From: Ron Message-ID: <44426d65-82a6-3ac5-958e-e7582ecaa7bd@gmail.com> Date: Wed, 6 Jun 2018 18:15:42 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <05FBE51B-5256-4756-8AE2-98850D3163AF@ciena.com> Content-Type: multipart/alternative; boundary="------------8E70289F064DB86BF6642286" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------8E70289F064DB86BF6642286 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 06/06/2018 01:54 PM, Moradhassel, Kavian wrote: > > To my mind, it makes perfect sense for columns to persist in the table > structure when dropped…the only question I have is whether the column > would survive a VACUUM FULL?  i.e. if the table is rewritten after the > column is dropped, would that change things? > > *Kav Moradhassel*|Ciena > > kmoradha@ciena.com |385 Terry Fox Drive > | Ottawa, ON, K2K 0L1  Canada > > +1 Another solution would be to dump/drop/create/load *just **that table*. -- Angular momentum makes the world go 'round. --------------8E70289F064DB86BF6642286 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit On 06/06/2018 01:54 PM, Moradhassel, Kavian wrote:

To my mind, it makes perfect sense for columns to persist in the table structure when dropped…the only question I have is whether the column would survive a VACUUM FULL?  i.e. if the table is rewritten after the column is dropped, would that change things?

 

Kav Moradhassel | Ciena

kmoradha@ciena.com | 385 Terry Fox Drive | Ottawa, ON, K2K 0L1  Canada


+1

Another solution would be to dump/drop/create/load just that table.

--
Angular momentum makes the world go 'round.
--------------8E70289F064DB86BF6642286--