Re: Waiting for select

It's doing something in slony. Part of the initial sync operation I
guess. I guess it must be doing an alter table or reindex or something.
I don't understand why though.

I'll repeat my question on the slony mailing list. Thanks for the
response.

__
Marc

On Fri, 2005-06-10 at 18:48 -0400, Tom Lane wrote:
> Marc Munro <marc(at)bloodnok(dot)com> writes:
> > Can someone explain this? I seem to have a query which is being blocked
> > by a lock. I was under the impression that selects are never blocked.
>
> AccessExclusiveLock blocks anything.
>
> > A query of blocking locks shows this:
>
> > object | trans | pid | mode | blocker
> > ---------------------------+-------+------+---------------------+---------
> > testdb.address_type | | 5754 | AccessExclusiveLock |
> > testdb.address_type | | 5987 | AccessShareLock | 5754
>
> So what's process 5754 doing?
>
> regards, tom lane