On Thu, May 18, 2017 at 5:41 PM, Scott Marlowe
wrote:
> On Thu, May 18, 2017 at 3:40 PM, Scott Marlowe
> wrote:
> > I would say that the best thing to do is to run 9.6 grab pgadmin4 and do
> all
> > the examples in the doc page on partitioning.
> >
> > https://www.postgresql.org/docs/9.6/static/
On Thu, May 18, 2017 at 3:40 PM, Scott Marlowe wrote:
> I would say that the best thing to do is to run 9.6 grab pgadmin4 and do all
> the examples in the doc page on partitioning.
>
> https://www.postgresql.org/docs/9.6/static/ddl-partitioning.html
>
> If that works well then the question becomes
I would say that the best thing to do is to run 9.6 grab pgadmin4 and do
all the examples in the doc page on partitioning.
https://www.postgresql.org/docs/9.6/static/ddl-partitioning.html
If that works well then the question becomes are there any esoteric cases
where pgadmin4 won't quite get you
On 5/18/2017 2:29 PM, Robert Eckhardt wrote:
All the code for creating and managing partitions is part of the core
Postgres code. What we are interested in looking into is what that
work flow might look like and how that workflow can be supported with
a GUI management tool.
only thing I'd e
On Thu, May 18, 2017 at 1:21 PM, Melvin Davidson
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
All the code for creating and managing partitions is part of the core
Postgres code. What we are interested in looking into is what that work
flow might look like and how that workflow can be supported with a GUI
management tool.
-- Rob
On Thu, May 18, 2017 at 3:21 PM, Melvin Davidson
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?
On Thu, May 18, 2017 at 2:10 PM, Shirley Wang wrote:
> Hello!
>
> We're a team from
