pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Aaron Weber <aweber@comcast.net>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Shaun Thomas <sthomas@optionshouse.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: how to improve perf of 131MM row table?
Date: Thu, 26 Jun 2014 16:40:51 -0400
Message-ID: <69dfd7f3-ccbb-4ae9-97f0-fcb99e7c9c18@email.android.com> (raw)
In-Reply-To: <CAMkU=1yxskTJ8ZQQZvBqJ82Jk_R_NoeuCKkYv+8aunT191=Htw@mail.gmail.com>
References: <53AB2CB1.8080201@comcast.net>
	<53AB35CC.10202@optionshouse.com>
	<1801a5d4-c3f1-4c0c-9c2c-ffb9d7f723a3@email.android.com>
	<CAMkU=1yxskTJ8ZQQZvBqJ82Jk_R_NoeuCKkYv+8aunT191=Htw@mail.gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>




>The PK of the master table and the PK of the detail table cannot be
>the same thing, or they would not have a master-detail relationship.
>One side has to be an FK, not a PK.
>
Of course this is correct. I was trying to make the point that there should be unique indices (of whatever flavor PG uses for PK's by default) on the relevant columns.  Since we're referring to a select statement, the actual integrity constraints should not come into play. 

I will remember to be more explicit about the schema next time. 



-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



view thread (25+ messages)  latest in thread

Message-ID: <69dfd7f3-ccbb-4ae9-97f0-fcb99e7c9c18@email.android.com>
Permalink:  ../69dfd7f3-ccbb-4ae9-97f0-fcb99e7c9c18@email.android.com/
Also on:    postgresql.org/message-id/69dfd7f3-ccbb-4ae9-97f0-fcb99e7c9c18@email.android.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: aweber@comcast.net, jeff.janes@gmail.com, sthomas@optionshouse.com
  Subject: Re: how to improve perf of 131MM row table?
  In-Reply-To: <69dfd7f3-ccbb-4ae9-97f0-fcb99e7c9c18@email.android.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox