| From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
|---|---|
| To: | "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: live metadata changes v8.3.4 |
| Date: | 2011-09-27 21:09:29 |
| Message-ID: | CABvLTWEs74e8CbrLBicANgRvbqZO_fohmwWvDwMrn73evTqA2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Sep 27, 2011 at 1:51 PM, Gauthier, Dave <dave(dot)gauthier(at)intel(dot)com> wrote:
> How does one make a metadata change to a DB that's actively being used.
> Specifically, I want to drop a view, drop some columns from a table that's
> used in the view, recreate the view without those columns.
BEGIN TRANSACTION;
DROP VIEW someView ...;
ALTER TABLE DROP COLUMN someColumn1, DROP COLUMN someColumn2;
CREATE VIEW someView AS ...;
COMMIT; --Wait for pre-existing locks to complete and hope your client
app doesn't break.
--
Regards,
Richard Broersma Jr.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2011-09-28 00:50:26 | Re: bytea columns and large values |
| Previous Message | pasman pasmański | 2011-09-27 20:55:13 | Re: New feature: accumulative functions. |