pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Litao Wu <litaowu@yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: reindex and copy - deadlock?
Date: Tue, 22 Jun 2004 08:00:42 -0700 (PDT)
Message-ID: <20040622150042.77663.qmail@web13125.mail.yahoo.com> (raw)
In-Reply-To: <18172.1086985673@sss.pgh.pa.us>

Hi,

I have changed "reindex table my_table" to:
psql ...
  -c "drop index my_index; create index my_index;"

We still experience the same "hang" problem.

I was told that this time, the process is
"create index my_index;" before the PG server is
bounced.

When I login the database, I found the 
my_index is still there.

I do not know what caused this happen, and I 
am also confused. If create index my_index is killed
by "-9", then my_index should not present in the
database because it has been dropped before creating.

On the other hand, if "drop index my_index;" is
killed, then how drop index (which is DDL, right?)
can be blocked? There must be other process(es)
has/have execlusive lock on my_index, which
is not our case from pg_locks.

Tom, we are in the process of installing 
the backend with --enable-debug.

Thanks,


--- Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Litao Wu <litaowu@yahoo.com> writes:
> > One difference between these two databases
> > is the one having REINDEX problem is using
> > NTFS file system. 
> 
> Oh?  That's interesting.
> 
> > Is it possible the root of problem?
> 
> I would not expect it to show this particular
> symptom --- if the
> backtrace is accurate.  But there are nearby places
> that might have
> FS-dependent behavior.  Can you do anything about my
> request for
> a stack trace from a debug-enabled build?
> 
> 			regards, tom lane



		
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail



view thread (16+ messages)  latest in thread

Message-ID: <20040622150042.77663.qmail@web13125.mail.yahoo.com>
Permalink:  ../20040622150042.77663.qmail@web13125.mail.yahoo.com/
Also on:    postgresql.org/message-id/20040622150042.77663.qmail@web13125.mail.yahoo.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: litaowu@yahoo.com, tgl@sss.pgh.pa.us
  Subject: Re: reindex and copy - deadlock?
  In-Reply-To: <20040622150042.77663.qmail@web13125.mail.yahoo.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox