so I have a pgsql function that will create tables based on MD for x
years in advance and inherits of base table.
with this
CHECK (_received >= '2013-01-01 00:00:00+11'::timestamp with time zone AND
_received < '2013-02-01 01:00:00+11'::timestamp with time zone)
now for the insert, do I
On 7/27/2017 12:43 AM, Alex Samad wrote:
... as long as the queries stay on a small amount of parts that we
should be okay.
thats true as long as the planner can restrict the queries to the
correct partition... but there's lots of queries that end up having to
hit all partitions because
So is date_trunc better than to_char ? I'm thinking it probably is
as for the number of partitions, well we don't plan on deleting anything,
but from my reading as long as the queries stay on a small amount of parts
that we should be okay.
A
On 27 July 2017 at 15:33, John R Pierce
On 7/26/2017 10:08 PM, Alex Samad wrote:
I have a large table about 3B rows, that I would like to partition on
a column called _received which is of type timestamp
a good goal is to have no more than about 100 partitions max, and
ideally more like 25.
when we partition on time stamp, we
Hi
I have a large table about 3B rows, that I would like to partition on a
column called _received which is of type timestamp
I followed this
https://medium.com/@StreamBright/creating-partitions-automatically-in-postgresql-7006d68c0fbb
and came up with
CREATE OR REPLACE FUNCTION
