Re: pg_migrator and making columns invisible

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: pg_migrator and making columns invisible
Date: 2009-06-02 14:07:11
Message-ID: 200906021407.n52E7Bx06695@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> 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?

FYI, one big problem with this is that if they rebuild the table before
dropping the columns the data is lost. It seems leaving the data around
as invalid might be safer.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-06-02 14:11:11 Re: [RFC,PATCH] SIGPIPE masking in local socket connections
Previous Message Robert Haas 2009-06-02 14:06:18 Re: explain analyze rows=%.0f