X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2D237D1C9DB for ; Thu, 12 Feb 2004 01:06:50 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 79158-10 for ; Wed, 11 Feb 2004 21:06:50 -0400 (AST) Received: from megazone.bigpanda.com (megazone.bigpanda.com [64.147.171.210]) by svr1.postgresql.org (Postfix) with ESMTP id 839F9D1C9BD for ; Wed, 11 Feb 2004 21:06:48 -0400 (AST) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 81799358FE; Wed, 11 Feb 2004 17:06:36 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 7FF3A358B5; Wed, 11 Feb 2004 17:06:36 -0800 (PST) Date: Wed, 11 Feb 2004 17:06:36 -0800 (PST) From: Stephan Szabo To: ow Cc: pgsql-sql@postgresql.org Subject: Re: 7.4 - FK constraint performance In-Reply-To: <20040212000610.13913.qmail@web60806.mail.yahoo.com> Message-ID: <20040211170317.M67403@megazone.bigpanda.com> References: <20040212000610.13913.qmail@web60806.mail.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/106 X-Sequence-Number: 16797 On Wed, 11 Feb 2004, ow wrote: > PostgreSQL 7.4 on i386-linux-gnu, compiled by GCC 2.96 > > -- about 10 records > CREATE TABLE my.Small > ( > id my.dint NOT NULL, > code my.dvalue NOT NULL, > CONSTRAINT pk_1 PRIMARY KEY (id), > ) WITHOUT OIDS; > > -- about 80M rows > CREATE TABLE my.Large > ( > id my.dlong NOT NULL, > small_id my.dint NOT NULL, > value my.value, > CONSTRAINT pk_2 PRIMARY KEY (id), > CONSTRAINT fk_2 FOREIGN KEY (small_id) REFERENCES my.small (id) ON UPDATE > RESTRICT ON DELETE RESTRICT, > ) WITHOUT OIDS; > > CREATE INDEX small_fk ON my.Large USING btree (small_id); > > --------------------------------------------- > The fowllowing queiries run in less than 40 ms. > 1) select 1 from Large where small_id = 239 > 2) SELECT 1 FROM ONLY "my"."Large" x WHERE "small_id" = 239 FOR UPDATE OF x > > 3) delete from Small where id = 239 > Feb 11 18:07:36 srv07 postgres[2091]: [91-1] LOG: statement: SELECT 1 FROM > ONLY "my"."Large" x WHERE "small_id" = $1 FOR UPDATE OF x Feb 11 18:10:41 srv07 > > postgres[2091]: [92-1] LOG: duration: 185273.262 ms > > When I try to delete record, it takes > 3 min. Why is it taking so long if > practically the same select query (see (2)) is running very quickly. Anything > that can be done to fix it? Hmm, I'd wonder if maybe it's choosing a sequential scan in the second case? As a random question, does increasing the statistics target on Large.small_id and re-analyzing change its behavior?