From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Steve Atkins <steve(at)blighty(dot)com> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Best options for new PG instance |
Date: | 2018-03-06 01:11:32 |
Message-ID: | 20180306011132.GE1878@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Mar 05, 2018 at 09:51:53AM -0800, Steve Atkins wrote:
> I've been running postgresql instances on ESXi VMs for years with no
> issues. I've not benchmarked them, but performance has been good
> enough despite their running on fairly wimpy hardware. Performance
> relative to bare metal is probably going to be dominated by disk IO,
> and depending on how you're hosting VMs that can be anywhere between
> pretty good and terrible - in a large corporation I'd expect it to be
> pretty good. Just don't skimp on RAM - having your hot data in the
> filesystem cache is always good and can make high latency storage
> tolerable.
One thing to be very careful about is the backup strategy of your
PostgreSQL instances. I would recommend primarily using PostgreSQL
in-core tools like pg_basebackup to do the work and make sure that
things are consistent. Users tend to rely a lot on VM snapshots,
particularly quiesced snapshots without memory footprint, but those
could be the cause of data corruption if not using appropriate
pre-freeze and post-thaw scripts in charge of freezing the partitions
while the snapshot is taken (use different partitions for the data
folder, pg_wal and logs as well!), so this would require extra work from
your side. I am talking about VMware technology here, still you can
find a lot of so-told-useful VM-level backup technologies. Be careful
with those as well when it comes to database backups. You can think
that your backups taken are safe, until you see a corruption which has
been hidden for weeks.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Raghavendra Rao J S V | 2018-03-06 01:54:03 | org.postgresql.util.PSQLException: Error could not open file "base/": No such file or directory |
Previous Message | rob stone | 2018-03-05 23:36:27 | Re: JDBC4 and setting statement_timeout: responds "is not yet implemented" |