| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Jada Case <jadac(at)mccright(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Adding field to a table currently being used |
| Date: | 2005-03-22 18:06:23 |
| Message-ID: | 1111514782.26897.1449.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, 2005-03-22 at 11:41, Jada Case wrote:
> Hello,
>
> I need to know if I add a field to an existing table within a database
> that is currently being accessed by many users, if it will effect it
> or crash it? I have researced the archives and could not find an
> answer, if there is documentation on this, will you point me in the
> right direction?
>
It definitely won't crash the server, PostgreSQL is quite robust.
Certain alter table actions may need to take out a short lived lock, but
shouldn't normally cause another client to fail, unless that client is
relying on a column that is being altered in some way that conflicts
with that client.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-03-22 18:37:32 | Re: Databases there, tables away |
| Previous Message | Bruno Wolff III | 2005-03-22 17:50:56 | Re: Whats the limit on the number of elements in the IN clause of SELECT/UPDATE/DELETE |