Re: ALTER TABLE schema SCHEMA TO new_schema?

From: Fernando Nasser <fnasser(at)redhat(dot)com>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER TABLE schema SCHEMA TO new_schema?
Date: 2002-12-02 15:35:34
Message-ID: 3DEB7DC6.2010801@redhat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joe Conway wrote:
> Christopher Kings-Lynne wrote:
>
>>> possible. We should probably just go with your suggestion. Anything else
>>> beyond the relnamespace and pg_depend entries that need to be dealt
>>> with?
>>
>>
>> What about sequences for serial columns? What about views or types that
>> depend on the table?
>>
>
> Yeah, good point. I think properly dealing with the pg_depends issues
> will catch anything of that nature, but what to do with them?
>
> Probably should move dependent type, constraint, index entries to the
> same new namespace. We might want to move related sequences, but I'm not
> sure we'd want to do that silently, since the sequence could be in use
> for other tables as well. And we should probably restrict the change if
> there are dependent functions or views. Does this capture the issues?
>

Why not just leave the sequence and types in the original schema and
make sure the table refers to them _there_? We just need to make sure
we have schema qualified references to the sequences and types.

Indexes, triggers (and constraints), toast tables etc. are related to
just one table so they can migrate together, I think.

--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser(at)redhat(dot)com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fernando Nasser 2002-12-02 15:37:38 Re: ALTER TABLE schema SCHEMA TO new_schema?
Previous Message Marc G. Fournier 2002-12-02 15:32:09 Re: Postgres 7.3 announcement on postgresql.org