Re: Rewriting DISTINCT and losing performance

From: Richard Huxton <dev(at)archonet(dot)com>
To: pgsql-performance(at)nullmx(dot)com
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Rewriting DISTINCT and losing performance
Date: 2007-05-21 11:40:21
Message-ID: 46518525.9010407@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Chuck D. wrote:
> Table "geo.city"
> Column | Type | Modifiers
> ------------+------------------------+-----------
> city_id | integer | not null
> state_id | smallint |
> country_id | smallint |
> latitude | numeric(9,7) |
> longitude | numeric(10,7) |
> city_name | character varying(100) |
> Indexes:
> "city_pk" PRIMARY KEY, btree (city_id)
> "idx_city_country_id" btree (country_id) CLUSTER
> Foreign-key constraints:
> "city_state_id_fk" FOREIGN KEY (state_id) REFERENCES geo.state(state_id)
> ON UPDATE CASCADE ON DELETE CASCADE

Any good reason why country_id is NULLable?

--
Richard Huxton
Archonet Ltd

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Chris Hoover 2007-05-21 14:42:54 Increasing Shared_buffers = slow commits?
Previous Message Josh Berkus 2007-05-21 09:14:14 Re: Rewriting DISTINCT and losing performance