From: | Sue Fitt <sue(at)inf(dot)ed(dot)ac(dot)uk> |
---|---|
To: | Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: setting up foreign keys |
Date: | 2006-08-11 11:48:01 |
Message-ID: | 44DC6E71.3030401@inf.ed.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Solved, it turned out to be a lock caused by a gui connected to the
database, even though the gui wasn't actually doing anything at the time...
Sue
Stephan Szabo wrote:
> On Thu, 10 Aug 2006, Sue Fitt wrote:
>
>
>> Hi all,
>>
>> This is my first post to the performance list, I hope someone can help me.
>>
>> I'm setting up a table with 2 columns, both of which reference a column
>> in another table:
>>
>> CREATE TABLE headwords_core_lexemes (
>> core_id int REFERENCES headwords_core(core_id),
>> lexeme_id int REFERENCES headwords_core(core_id),
>> );
>>
>> Trouble is, it's taken 18 hours and counting!
>>
>
> What precisely is taking the time, the create table itself? The only thing
> that the create should be waiting for as far as I know is a lock on
> headwords_core to add the triggers.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
> choose an index scan if your joining column's datatypes do not
> match
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Spiegelberg, Greg | 2006-08-11 19:01:15 | Re: setting up foreign keys |
Previous Message | Thomas Pundt | 2006-08-11 09:34:49 | Re: Slow access to PostgreSQL server |