Re: pg_migrator and making columns invisible

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_migrator and making columns invisible
Date: 2009-06-02 14:29:08
Message-ID: 11718.1243952948@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeremy Kerr 2009-06-02 14:36:06 Re: [RFC,PATCH] SIGPIPE masking in local socket connections
Previous Message Tom Lane 2009-06-02 14:24:02 Re: [RFC,PATCH] SIGPIPE masking in local socket connections