Re: [GENERAL] PG 10 - Trouble with overlap of range partition of two dimensions

2017-11-01 Thread Arjen Nienhuis
On Nov 1, 2017 02:41, "Stephen Froehlich" wrote: Hi Michael, So if I'm reading this correctly, the proper way to do my use case is to use partitions of partitions, right? Or maybe reverse the order of the columns: PARTITION BY RANGE (source_no, start_time)

Re: [GENERAL] PG 10 - Trouble with overlap of range partition of two dimensions

2017-10-31 Thread Stephen Froehlich
Hi Michael, So if I'm reading this correctly, the proper way to do my use case is to use partitions of partitions, right? --Stephen -Original Message- From: Michael Paquier [mailto:michael.paqu...@gmail.com] Sent: Tuesday, October 31, 2017 4:06 PM To: Stephen Froehlich

Re: [GENERAL] PG 10 - Trouble with overlap of range partition of two dimensions

2017-10-31 Thread Michael Paquier
On Tue, Oct 31, 2017 at 8:36 PM, Stephen Froehlich wrote: > CREATE TABLE lotsa_data_20171027_src3 PARTITION OF lotsa_data > FOR VALUES FROM ('2017-10-26 18:00:00-06', 3) TO ('2017-10-27 > 17:59:59.999-06', 3); > ERROR: partition " lotsa_data_20171027_src1" would

[GENERAL] PG 10 - Trouble with overlap of range partition of two dimensions

2017-10-31 Thread Stephen Froehlich
So I have a table that has two fields I want to partition by: CREATE TABLE lotsa_data ( start_time timestamp with time zone, source_nointeger, counter integer) PARTITION BY RANGE (start_time, source_no); CREATE TABLE lotsa_data_20171027_src1 PARTITION OF lotsa_data FOR VALUES FROM