On Sep 7, 2013, at 6:54, Steve Atkins st...@blighty.com wrote:
On Sep 6, 2013, at 9:37 PM, François Beausoleil franc...@teksol.info wrote:
Le 2013-09-07 à 00:29, Steve Atkins a écrit :
If I have a partitioned table that has some range constraints that look
kinda like they're intended for
Alban Hertroys haram...@gmail.com writes:
On Sep 7, 2013, at 6:54, Steve Atkins st...@blighty.com wrote:
If I have a partitioned table that has some range constraints that look
kinda like they're intended for constraint exclusion, but aren't quite
non-overlapping, will that break anything?
On Sep 7, 2013, at 7:20 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Alban Hertroys haram...@gmail.com writes:
On Sep 7, 2013, at 6:54, Steve Atkins st...@blighty.com wrote:
If I have a partitioned table that has some range constraints that look
kinda like they're intended for constraint
If I have a partitioned table that has some range constraints that look kinda
like they're intended for constraint exclusion, but aren't quite
non-overlapping, will that break anything?
e.g.
create table jan ( …, check(created = '2013-01-01' and created
'2013-02-01'), check(id =0 and id
Le 2013-09-07 à 00:29, Steve Atkins a écrit :
If I have a partitioned table that has some range constraints that look kinda
like they're intended for constraint exclusion, but aren't quite
non-overlapping, will that break anything?
e.g.
create table jan ( …, check(created =
On Sep 6, 2013, at 9:37 PM, François Beausoleil franc...@teksol.info wrote:
Le 2013-09-07 à 00:29, Steve Atkins a écrit :
If I have a partitioned table that has some range constraints that look
kinda like they're intended for constraint exclusion, but aren't quite
non-overlapping, will
