pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Sue Fitt <sue@inf.ed.ac.uk>
To: pgsql-performance@postgresql.org
Subject: Re: setting up foreign keys
Date: Thu, 10 Aug 2006 10:04:55 +0100
Message-ID: <44DAF6B7.1090800@inf.ed.ac.uk> (raw)
In-Reply-To: <44DAEB04.9050306@gmail.com>
References: <44DAE8CF.1030107@inf.ed.ac.uk>
	<44DAEB04.9050306@gmail.com>

Thanks Chris and Chris, you've solved it.

I had a gui open that connects to the database. It was doing nothing 
(and not preventing me adding to or altering headwords_core via psql), 
but having closed it the table is instantly created. Weird.

BTW, referencing the same column twice is deliberate, it's a 
cross-reference.

Sue

Chris Mair wrote:
 >> 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!  The table 
headwords_core only has about 13,000 lines, and core_id is the primary 
key on that table. However, I assume it must be those 13,000 lines that 
are the problem, since if I try it referencing a similar table with 360 
lines the new table is created almost instantly.
 >>    
 >
 > Hi,
 >
 > the 13000 rows in headwords_core don't matter at all for what this
 > statement concerns. I bet you have another idle transaction that keeps
 > headwords_core locked, for example because you did an
 > alter table headwords_core there...
 >
 > Bye,
 > Chris.
 >
 >



view thread (12+ messages)  latest in thread

Message-ID: <44DAF6B7.1090800@inf.ed.ac.uk>
Permalink:  ../44DAF6B7.1090800@inf.ed.ac.uk/
Also on:    postgresql.org/message-id/44DAF6B7.1090800@inf.ed.ac.uk

 · 

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: sue@inf.ed.ac.uk
  Subject: Re: setting up foreign keys
  In-Reply-To: <44DAF6B7.1090800@inf.ed.ac.uk>

* 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