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
Marc Munro <[EMAIL PROTECTED]> 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 | t
Marc Munro wrote:
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.
Am I missing something or is this bad behaviour?
Do you happen to be running a vacuum full?
I am using slony and am synchronising
