From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Dane Foster <studdugie(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Can PostgreSQL use multi-column index for FK constraint validation? |
Date: | 2016-01-26 20:54:14 |
Message-ID: | 15290.1453841654@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Dane Foster <studdugie(at)gmail(dot)com> writes:
> My example is modeling an order details table and the answer to the
> question of selectivity is it depends. For some of our clients it is highly
> selective because customers generally order a single item at a time. For
> others it's multi-modal because it starts out w/ their customers ordering
> only a single item but over time customer behavior changes and there is
> this mix of single and multi item orders. Additionally my use case for
> PostgreSQL is the VPS use case where each client has their own schema so
> I'd prefer not to have to deal w/ per client index building and
> maintenance. So is there a rule of thumb design wise for variable
> selectivity as I've described?
See
http://www.postgresql.org/docs/9.4/static/indexes.html
particularly sections 11.3 and 11.5.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2016-01-26 20:57:04 | Re: Can PostgreSQL use multi-column index for FK constraint validation? |
Previous Message | Dane Foster | 2016-01-26 20:47:44 | Re: Can PostgreSQL use multi-column index for FK constraint validation? |