Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-sql-owner+archive@lists.postgresql.org>)
	id 1hEaKQ-0006X4-Sx
	for pgsql-sql@arkaria.postgresql.org; Thu, 11 Apr 2019 14:05:23 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-sql-owner+archive@lists.postgresql.org>)
	id 1hEaKP-0007VJ-GD
	for pgsql-sql@arkaria.postgresql.org; Thu, 11 Apr 2019 14:05:21 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <alessard@mapgears.com>)
	id 1hEaKP-0007SO-38
	for pgsql-sql@lists.postgresql.org; Thu, 11 Apr 2019 14:05:21 +0000
Received: from smtp78.iad3b.emailsrvr.com ([146.20.161.78])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <alessard@mapgears.com>)
	id 1hEaKI-0002n7-VS
	for pgsql-sql@lists.postgresql.org; Thu, 11 Apr 2019 14:05:19 +0000
Received: from smtp18.relay.iad3b.emailsrvr.com (localhost [127.0.0.1])
	by smtp18.relay.iad3b.emailsrvr.com (SMTP Server) with ESMTP id 31593E0292
	for <pgsql-sql@lists.postgresql.org>; Thu, 11 Apr 2019 10:05:14 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mapgears.com;
	s=20190410-l25oaji6; t=1554991514;
	bh=hPkqBVNf2hPeqxw0sJFLO9n/4fu1Ub4j51R8gWIEUCg=;
	h=To:From:Subject:Date:From;
	b=Cufr9KLKWc8UsI64dxKvHfYUjO8PNmvLuTfPwQ+boQ1ciHQ3eRNQIKrUN7YV1fn/B
	 Nd+L/ouMWFE9PqGbq+R9WN1OA94tblKBzQE40bdEia4aDJoNs1xTyD0UGutJAW77Dd
	 2nXmbYIarymIVDlKBOnl9+S3N77bIKmCvEP9O88Y=
X-Auth-ID: alessard@mapgears.com
Received: by smtp18.relay.iad3b.emailsrvr.com (Authenticated sender:
 alessard-AT-mapgears.com) with ESMTPSA id 02523E028C
	for <pgsql-sql@lists.postgresql.org>; Thu, 11 Apr 2019 10:05:13 -0400 (EDT)
X-Sender-Id: alessard@mapgears.com
Received: from [192.168.4.190] (modemcable098.185-37-24.static.videotron.ca
 [24.37.185.98])
	(using TLSv1.2 with cipher AES128-SHA)
	by 0.0.0.0:465 (trex/5.7.12);
	Thu, 11 Apr 2019 10:05:14 -0400
To: pgsql-sql@lists.postgresql.org
From: Alexandre Lessard <alessard@mapgears.com>
Subject: Partitioning table on tztsrange
Message-ID: <ab10cb25-a779-512b-5934-d8711db40496@mapgears.com>
Date: Thu, 11 Apr 2019 10:05:13 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
List-Id: <pgsql-sql.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-sql@lists.postgresql.org>
List-Owner: <mailto:pgsql-sql-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-sql>
Precedence: bulk

Hi psql users,

I'm looking into implementing a partitioning solution for one of our 
table that has a lot of data. The catch here is that our filter index is 
on a tstzrange and all our code is using the range functions to filter 
the data.

I'd like to know if it's possible to use a tstzrange as the partition 
key column and if so, how is it configured on the sub tables for the limits.

What I'd like to do is configure the partitions on the lower value of 
the tstzrange.

Thanks for your help.

Alexandre Lessard
Mapgears