Re: Call for users to talk about table partitioning

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Melvin Davidson <melvin6925(at)gmail(dot)com>
Cc: Shirley Wang <swang(at)pivotal(dot)io>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Robert Eckhardt <reckhardt(at)pivotal(dot)io>
Subject: Re: Call for users to talk about table partitioning
Date: 2017-05-18 21:35:20
Message-ID: CAOR=d=0Kx1y3HS3Gd04ELf7q-pc9cvDgvr180feHL_sODa-7AA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 18, 2017 at 1:21 PM, Melvin Davidson <melvin6925(at)gmail(dot)com>
wrote:

> Shirley,
> I am a bit confused. AFAIK, it is PostgreSQL that is responsible for table
> partitioning. PgAdmin4 is just an administrative tool.
> Are you saying that PgAdmin4 now can make partition tables automatically?
>

I think maybe she just means that their GUI is pgadmin4 for reference as
opposed to the partitioning being IN pgadmin4.

If she'd like to set up a discussion thread HERE on partitioning I'm more
than willing to add to it.

More importantly, while I think the postgresql documentation on
partitioning gives you everything you need to roll your own, it doesn't
inform you on all the ways to do partitioning for various jobs. That's
where partitioning gets interesting and requires business requirements and
all that fun stuff.

Do you hand off maintenance jobs to cron or do you check and run it every
time a function's called etc.

Do you put materialized views on top to stop scanning all the partitions
ever?

fun fun.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2017-05-18 21:38:53 Re: Call for users to talk about table partitioning
Previous Message Robert Eckhardt 2017-05-18 21:29:23 Re: Call for users to talk about table partitioning