| From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
|---|---|
| To: | Roman Fail <rfail(at)posportal(dot)com> |
| Cc: | <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: 7.3.1 New install, large queries are slow |
| Date: | 2003-01-17 07:00:48 |
| Message-ID: | 20030116225602.G17408-100000@megazone23.bigpanda.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, 16 Jan 2003, Roman Fail wrote:
> > Stephan Szabo wrote:
> > Also you have two indexes on batchdetailid right now (primary key
> > also creates one) which added to the confusion.
>
> The 7.3.1 docs for CREATE TABLE don't mention anything about automatic
> index creation for a PRIMARY KEY. I didn't see any PK indexes via
> pgAdminII, so I read this line from the docs and decided to create
> them separately.
> "Technically, PRIMARY KEY is merely a combination of UNIQUE and NOT NULL"
Right, but the implementation of UNIQUE constraints in postgresql right
now is through a unique index. That's not necessarily a guarantee for
the future, but for right now you can rely on it.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Timur Irmatov | 2003-01-17 11:48:00 | index usage |
| Previous Message | Tom Lane | 2003-01-17 06:06:10 | Re: 7.3.1 New install, large queries are slow |