X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A0FA7D1B191 for ; Tue, 22 Jun 2004 12:00:54 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 96534-06 for ; Tue, 22 Jun 2004 15:00:48 +0000 (GMT) Received: from web13125.mail.yahoo.com (web13125.mail.yahoo.com [216.136.174.143]) by svr1.postgresql.org (Postfix) with SMTP id 5A413D1B737 for ; Tue, 22 Jun 2004 12:00:44 -0300 (ADT) Message-ID: <20040622150042.77663.qmail@web13125.mail.yahoo.com> Received: from [63.78.248.48] by web13125.mail.yahoo.com via HTTP; Tue, 22 Jun 2004 08:00:42 PDT Date: Tue, 22 Jun 2004 08:00:42 -0700 (PDT) From: Litao Wu Subject: Re: reindex and copy - deadlock? To: Tom Lane Cc: pgsql-performance@postgresql.org In-Reply-To: <18172.1086985673@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/226 X-Sequence-Number: 7284 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 wrote: > Litao Wu 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