Re: Partioning with overlapping and non overlapping constraints - Mailing list pgsql-general

From David G Johnston
Subject Re: Partioning with overlapping and non overlapping constraints
Date
Msg-id 1423192376715-5836871.post@n5.nabble.com
Whole thread Raw
In response to Partioning with overlapping and non overlapping constraints  (Tim Uckun <timuckun@gmail.com>)
Responses Re: Partioning with overlapping and non overlapping constraints
List pgsql-general
Tim Uckun wrote
> 1. Should I be worried about having possibly hundreds of thousands of
> shards.

IIRC, yes.


> 2. Is PG smart enough to handle overlapping constraints on table and limit
> it's querying to only those tables that have the correct time constraint.

Probably yes, but seems easy enough to verify.

All constraints are checked for each partiton and if any return false the
entire partiton will be excluded; which means multiple partitions can be
included.

Note, this is large reason why #1 poses a problem.

David J.




--
View this message in context:
http://postgresql.nabble.com/Partioning-with-overlapping-and-non-overlapping-constraints-tp5836869p5836871.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


pgsql-general by date:

Previous
From: Tim Uckun
Date:
Subject: Partioning with overlapping and non overlapping constraints
Next
From: Tim Smith
Date:
Subject: Re: Using row_to_json with %ROWTYPE ?