Re: pg_migrator and making columns invisible - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_migrator and making columns invisible
Date
Msg-id 200906021517.n52FHjc08861@momjian.us
Whole thread Raw
In response to Re: pg_migrator and making columns invisible  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > pg_migrator requies tables using tsvector data types to be rebuilt, and
> > there has been discussion of how to prevent people from accessing those
> > columns before they are rebuilt.  We discussed renaming the tables
> > (affects all columns) or columns, using rules (not fine-grained enough),
> > or using column permissions (doesn't affect super-users).
> 
> > My new idea is to mark the column as "dropped" and unmark them before
> > rebuilding the table.  That might be the best I can do.  Comments?
> 
> You're expending a lot of work on solving the wrong problem.  The right
> solution is a temporary data type.

How do cleanup all references to the tsvector data type?  I am afraid
there will be tons of tsvector references outside tables that I can't
clean up.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Win32 link() function
Next
From: "Markus Wanner"
Date:
Subject: Re: PostgreSQL Developer meeting minutes up