Explicit Named Indexes for Constraints - Mailing list pgsql-general

From Jeff Larsen
Subject Explicit Named Indexes for Constraints
Date
Msg-id d1f9b6f00710211124h729b1aachba527026a2eff848@mail.gmail.com
Whole thread Raw
Responses Re: Explicit Named Indexes for Constraints  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I'm new to PosgtreSQL, a veteran with Informix. We are considering a migration.

In Informix, it is recommended to create explicit named indexes on
columns for primary and foreign keys prior to creating the
constraints. Otherwise, the server create the indexes for you with
meaningless names. This is not generally a problem, except when you
dump the schema, you get all the constraint indexes in the DDL,
exported as if they were explicitly created, but with the server
generated names. It's a mess to sort through.

What's the recommended procedure in PG?  At first glance it appears
that PG hides the implicit indexes from you at all times, including
pg_dump. So it appears that explicit index creation can be skipped
without leaving you with a mess later. Is this just a non-issue in PG?

Jeff

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: keeping an index in memory
Next
From: Dave Cramer
Date:
Subject: Re: looking for some real world performance numbers