From: | Jaime Soler <jaime(dot)soler(at)gmail(dot)com> |
---|---|
To: | ghiureai <isabella(dot)ghiurea(at)nrc-cnrc(dot)gc(dot)ca> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: PGSQL as database server container |
Date: | 2017-02-22 14:33:59 |
Message-ID: | CAKVUGgS-JzxzNBi080652n5TgERfOAWRHOy3YghoD+D4zUjhFA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
In my opinion the big problem is containers are recommended for stateless
applications and people would like to use them to stateful applications
like relational databases so storage is your problem. There are some
storage ( plugins ) solutions some of them have a one node scope and other
cluster wide. Take a look to this storage solution
https://github.com/portworx/px-dev
2017-02-21 17:17 GMT+01:00 ghiureai <isabella(dot)ghiurea(at)nrc-cnrc(dot)gc(dot)ca>:
> Hi List,
>
> I'm looking to get some feedback from your own experience using PGSQL as
> a database containers, form what I had been reading I found more user cases
> for LXD and Docker with latest PGSQL ,is this assumption correct ? What
> is feedback, should we consider LXD and OpenStack also , how about the
> basic requirements I need to put for Sysadmin when config PGSQL as
> database server container? ( memeory, layout of PG files etc?)
>
> Thank you
> Isabella
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Jaime Soler | 2017-02-22 16:45:16 | Re: Issue related to audit trigger after upgrade to Postgresql9.6 |
Previous Message | Jaime Soler | 2017-02-22 14:23:00 | Re: Best system for a data warehouse application |