Skip site navigation (1) Skip section navigation (2)

Re: How would I "close" a atble?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: How would I "close" a atble?
Date: 2007-12-18 04:25:33
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
"Tena Sakai" <tsakai(at)gallo(dot)ucsf(dot)edu> writes:
> That pid 6697 caught my interest and I fished it out of "ps -ef":
>   postgres  6697  4916  0 Dec15 ?        00:19:45 postgres: postgres canon [local] REINDEX waiting
> (and for the sake of completeness...)
>   postgres 12930  4916  0 11:24 ?        00:00:00 postgres: gbrush canon SELECT waiting
>   postgres 18177  4916  0 Dec15 ?        00:00:02 postgres: gbrush canon SELECT waiting
>   postgres 18825  4916  0 12:55 ?        00:00:00 postgres: tsakai canon SELECT waiting

The deal here is that the REINDEX is blocked trying to get exclusive
lock on table 16496, while those other guys are (apparently) stacked
up behind it.  What you have not shown us is what transaction has
actually *got* a lock on 16496.

> I could kill this process from unix
> level, but before I do so, would you please comment as to why
> this might have happened and what repercussion might I have
> from killing it, if any?

kill -INT would probably be safe enough, but you should first look into
what is blocking the REINDEX from going through.

			regards, tom lane

In response to


pgsql-admin by date

Next:From: Tena SakaiDate: 2007-12-18 06:25:54
Subject: Re: How would I "close" a atble?
Previous:From: Benjamin KrajmalnikDate: 2007-12-18 04:09:42
Subject: Re: Looking for an E/R tool for Postgres

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group