Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Performance Issues
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com>
- Cc: Dhanaraj(dot)M(at)Sun(dot)COM, Mark Woodward <pgsql(at)mohawksoft(dot)com>, Richard Huxton <dev(at)archonet(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Performance Issues
- Date: Wed, 24 May 2006 00:28:02 -0400
- Message-id: <25494(dot)1148444882(at)sss(dot)pgh(dot)pa(dot)us>
Christopher Kings-Lynne <chris(dot)kings-lynne(at)calorieking(dot)com> writes: >> Thank you for your help. I found that an implicit index is created for >> the primary key in the current version. However, it is not done in 7.x >> version. > It absolutely is created in all 7.x versions of PostgreSQL. And every other version too. PRIMARY KEY/UNIQUE syntax was not supported before this patch: 1997-12-04 18:07 thomas * src/backend/parser/: analyze.c, gram.y: Add SQL92-compliant syntax for constraints. Implement PRIMARY KEY and UNIQUE clauses using indices. and in that patch and every subsequent version, unique constraints are associated with indexes. In fact, we do not even *have* any implementation method for unique constraints other than the duplicate- entry-detection code in the btree index AM. regards, tom lane
- References:
- Performance Issues
- From: Dhanaraj M
- Re: Performance Issues
- From: Richard Huxton
- Re: Performance Issues
- From: Mark Woodward
- Re: Performance Issues
- From: Dhanaraj M
- Re: Performance Issues
- From: Christopher Kings-Lynne
- Performance Issues
- Prev by Date: Re: Performance Issues
- Next by Date: Re: LIKE, leading percent, bind parameters and indexes
- Previous by thread: Re: Performance Issues
- Next by thread: Why is CVS server so slow?
- Indexes: