pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
Date: Wed, 6 Jun 2018 18:15:42 -0500
Message-ID: <44426d65-82a6-3ac5-958e-e7582ecaa7bd@gmail.com> (raw)
In-Reply-To: <05FBE51B-5256-4756-8AE2-98850D3163AF@ciena.com>
References: <CACq6szQbQDG6_mThyH32=6J0e99-KdqOrhZMm9QwvGoVFzNbBw@mail.gmail.com>
	<CAOC+FBXehj4X2DMfytnPKHRWrWWZjq1G9OfUXsMop5Tex7hrvg@mail.gmail.com>
	<3C61E858-5CA7-405D-B32A-B4C89D1AC62E@elevated-dev.com>
	<CACq6szR7Q--tw67ZJL4-T59oAXCLXgmCDFVh=FunY3N4HCDLXg@mail.gmail.com>
	<CAOC+FBX6JLtcz-vO7K1rB-qmn23MyVgHya5xgcYLX-yUYoM_xw@mail.gmail.com>
	<05FBE51B-5256-4756-8AE2-98850D3163AF@ciena.com>

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 <mailto:kmoradha@ciena.com> |385 Terry Fox Drive 
> | Ottawa, ON, K2K 0L1  Canada
>
> <mailto:wellsoliver@gmail.com>

+1

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

-- 
Angular momentum makes the world go 'round.

view thread (14+ messages)  latest in thread

Message-ID: <44426d65-82a6-3ac5-958e-e7582ecaa7bd@gmail.com>
Permalink:  ../44426d65-82a6-3ac5-958e-e7582ecaa7bd@gmail.com/
Also on:    postgresql.org/message-id/44426d65-82a6-3ac5-958e-e7582ecaa7bd@gmail.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
  Subject: Re: [**EXTERNAL**] Re: [pgsql-admin] "Soft-hitting" the 1600 column limit
  In-Reply-To: <44426d65-82a6-3ac5-958e-e7582ecaa7bd@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox