Postgres Pro
Downloads
Home   >   mailing lists

Re: Must I create an index for child table if master table have one? - Mailing list pgsql-general

From Melvin Davidson
Subject Re: Must I create an index for child table if master table have one?
Date
Msg-id CANu8Fixuo02RmrVJKUzB8X82A8CMqQ=Vg1+foVe3GiVKnrP2ug@mail.gmail.com
Whole thread Raw
In response to Re: Must I create an index for child table if master table have one?  (Melvin Davidson <melvin6925@gmail.com>)
List pgsql-general
Tree view
To clarify, if you are talking about partitioning, then you almost certainly want to create a similar index on the child table.
If you are referring to a Foreign Key Constraint, then it is also good idea to make that index, but not necessary.

On Tue, Nov 8, 2016 at 1:46 PM, Melvin Davidson <melvin6925@gmail.com> wrote:


On Tue, Nov 8, 2016 at 1:33 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Tue, Nov 8, 2016 at 11:08 AM, Edmundo Robles <edmundo@sw-argos.com> wrote:
Hi!

 i have a  simple question,  if the master table have an index, must  i have create  the same index in a child  table?
what is  the best practice  for  indexes  in table partition ?

Indexes are self-contained within the physical table on which they are defined.  The index on the master contains no rows that are present in the child table.

David J.​


>Indexes are self-contained within the physical table on which they are defined
IOW, yes.

--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.



--
Melvin Davidson
I reserve the right to fantasize.  Whether or not you
wish to share my fantasy is entirely up to you.

pgsql-general by date:

Previous
From: Melvin Davidson
Date:
Subject: Re: Must I create an index for child table if master table have one?
Next
From: Oleg Bartunov
Date:
Subject: Re: Gin indexes on intarray is fast when value in array does not exists, and slow, when value exists