From: | Claire McLister <mclister(at)zeesource(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql general list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Create index hanging |
Date: | 2006-07-21 12:17:49 |
Message-ID: | B650437D-296D-436F-8EE8-96A185FBC162@zeesource.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Yes, that could be the case. We have a python function that imports
CSV files, which can take a long time, and that may have been running
during that time. I didn't look at the pg_lock file. What should I be
looking for?
On Jul 20, 2006, at 3:13 PM, Tom Lane wrote:
> Claire McLister <mclister(at)zeesource(dot)net> writes:
>> We have a couple of tables (40,000 and 600,000 rows each) that I am
>> trying to build an index on an integer column.
>
>> When I issue the "create index foo_index on foo(id);" command in
>> psql it just does not return. I've waited over half an hour for the
>> smaller table.
>
> It sounds like someone had a write lock on the table. Did you try
> looking in pg_locks?
>
> regards, tom lane
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | AL ELK | 2006-07-21 12:37:44 | PGSQL 8.1.4 on Win2003 at istanbul :), could not access status of transaction xxxxx , could not open file "pg_subtrans/000A": Invalid argument |
Previous Message | Christian Rengstl | 2006-07-21 10:55:01 | problem with windows installer |