Re: Rewriting DISTINCT and losing performance
От | Richard Huxton |
---|---|
Тема | Re: Rewriting DISTINCT and losing performance |
Дата | |
Msg-id | 46518525.9010407@archonet.com обсуждение исходный текст |
Ответ на | Rewriting DISTINCT and losing performance ("Chuck D." <pgsql-performance@nullmx.com>) |
Ответы |
Re: Rewriting DISTINCT and losing performance
|
Список | 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
В списке pgsql-performance по дате отправления: