| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Stas Oskin <stas(at)neo(dot)co(dot)il> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Postgres locks table schema? |
| Date: | 2005-09-21 19:53:45 |
| Message-ID: | 1127332425.30825.61.camel@state.g2switchworks.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2005-09-21 at 12:51, Stas Oskin wrote:
> Hi.
>
>
>
> When running SQL scripts, which change the tables' schema, we
> sometimes experience a lock of these tables' schema. The lock occurs
> on the first command of the script, on the first modified table. When
> this occurs, no further schema modification for this table is
> possible, until the server is restarted, which is very problematic for
> a production environment.
>
>
>
> Perhaps someone is familiar with this behavior, and how it can be
> resolved, without the restart of the server?
>
>
>
> The server used is PostgreSQL 8.0.3, and the OS is Fedora Core 3.
Have you got a test case that reproduces this in some way? I'm guessing
Tom's got it right on committing the transaction, but without knowing
EXACTLY what you're doing, we're just guessing here.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2005-09-21 19:54:54 | Re: Fetching column names for a table |
| Previous Message | Cristian Prieto | 2005-09-21 19:51:21 | COPY and Unicode... |