Thanks. I'll look into this next time it happens.
For now, I tried the create index commands again, and they worked in
a split-second. So, it must have been the lock contention, and not
the VACUUM'ng.
On Jul 21, 2006, at 6:45 AM, Tom Lane wrote:
Claire McLister <[EMAIL PROTECTED]> writes:
On Fri, 2006-07-21 at 14:17, Claire McLister wrote:
> 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?
I have the
Claire McLister <[EMAIL PROTECTED]> writes:
> 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?
A record with grant
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 <[EMAIL
Claire McLister <[EMAIL PROTECTED]> 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 hou
No, this is a brand new index, so no drops.
On Jul 20, 2006, at 2:03 PM, Ian Harding wrote:
On 7/20/06, Claire McLister <[EMAIL PROTECTED]> wrote:
Hi,
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 "crea
Thanks. Haven't VACUUMed ever. (Sloppy housekeeping:-)
Will do so and let you know if it helped.
There seems to have been some other problem too. I had to just now
forcefully shut down the postmaster and re-start it as it was
beginning to block on other requests as well.
If I Ctl-C the PS
