On Sun, Jun 18, 2017 at 2:20 PM, Condor <condor@xxxxxxxxxx> wrote: > Hello ppl, > > a few years ago I asked the same question but did not receive valued answers > and we use different way to realize the project. > Today I wanna ask did some one do it and most important for me, can some one > share his experience ? > What I should expect, what is good and bad things that can be happened. > > Im thinking the problems can be occurred if server is restarted and data is > not synced, but for that is raid cache battery. > Also if hard drive need to be checked for bad clusters or broken index / > files on filesystem what will happened with data? > Because postgresql does not support data level encryption, Im wanna realize > with third party tools. The one and only time I setup a server to us LUKS was for a demo laptop so that if it was lost our code / data / db etc etc were not accessible. In that instance we didn't test for fsync reliability because it was an easily recreateable system. Generally speaking PostgreSQL expects "perfect" storage that writes when it says it writes and doesn't present bad sectors to the database to handle but rather maps such sectors out of the way silently without data corruption. I think the only real test here is to build a luks system, initiate some pgbench type runs, wait a minute, run checkpoint and then yank out the plug. Run a dozen or so times looking for data corruption. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
