pg.ddx.io pgsql-pkg-docker@postgresql.org mailing list archive
help / color / mirror / Atom feedVolumes vs. UFS storage
2+ messages / 2 participants
[nested] [flat]
* Volumes vs. UFS storage
@ 2014-07-14 19:02 Josh Berkus <josh@agliodbs.com>
0 siblings, 1 reply; 2+ messages in thread
From: Josh Berkus @ 2014-07-14 19:02 UTC (permalink / raw)
To: pgsql-pkg-docker
Tianon, Yosif:
Another development vs. production question we have is configuring the
main package to have a volume "option". For production installations,
users are going to want to put $PGDATA on a volume linked to a specific
local drive location, but users running automated tests will not want to
(as well as users who don't care about DB performance).
Thoughts on this?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
--
Sent via pgsql-pkg-docker mailing list (pgsql-pkg-docker@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-docker
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Volumes vs. UFS storage
@ 2014-07-14 19:32 Joseph Ferguson <joe@infosiftr.com>
parent: Josh Berkus <josh@agliodbs.com>
0 siblings, 0 replies; 2+ messages in thread
From: Joseph Ferguson @ 2014-07-14 19:32 UTC (permalink / raw)
To: Josh Berkus <josh@agliodbs.com>; +Cc: pgsql-pkg-docker
On Mon, Jul 14, 2014 at 1:02 PM, Josh Berkus <josh@agliodbs.com> wrote:
> Tianon, Yosif:
>
> Another development vs. production question we have is configuring the
> main package to have a volume "option". For production installations,
> users are going to want to put $PGDATA on a volume linked to a specific
> local drive location, but users running automated tests will not want to
> (as well as users who don't care about DB performance).
>
> Thoughts on this?
The volume is exposed in the Dockerfile, but users don't have to
provide a --volumes-from or -v bind mount to make it run. See the
docs for more info about volumes[1]. If they run it for testing
without one of these options it will just be using storage local to
that container and will be deleted when the container is deleted.
Example automated test:
docker run --name my-test-pgsql -d postgres
docker run --link my-test-pgsql:postgres -it my-testing-image
docker stop my-test-pqsql
docker rm my-test-pgsql
The container including the $PGDATA directory will be deleted on docker rm.
Production example:
docker run --name prod-pgsql1 -d -v
/host/path/to/raid:/var/lib/postgresql/data postgres
docker run --name prod-app1 --link prod-pgsql1:postgres -d my-app
[1]: https://docs.docker.com/userguide/dockervolumes/
- Joe Ferguson :: joe@infosiftr.com
InfoSiftr :: Vice President of Programming
--
Sent via pgsql-pkg-docker mailing list (pgsql-pkg-docker@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-pkg-docker
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2014-07-14 19:32 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2014-07-14 19:02 Volumes vs. UFS storage Josh Berkus <josh@agliodbs.com>
2014-07-14 19:32 ` Joseph Ferguson <joe@infosiftr.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox