4 ms·
Using the distro-supplied packages for PG (or any database server) is typically not the best choice for a production deployment.
by dboreham 10y ago
Using the distro-supplied packages for PG (or any database server) is typically not the best choice for a production deployment.
- peteretep 10y ago> Using the distro-supplied packages for PG > (or any database server) Or almost any of your application environment, really.
- elktea 10y agoDistro supplied packages are a handy way of receiving timely security fixes without keeping too close an eye on recent CVEs + application changelogs.
- pritambaral 10y agoFor regular packages, sure. But for highly-active, well-maintained codebases like postgres – who package their software for your OS, upstream is going to be quicker with security fixes than distro.
- Roritharr 10y agoI would like to hear more about that. Our Server Team swears on using CentOS Packages with Backports for everything for security purposes. This slows us a bit down, but so far we haven't had any security or audit related issues. How do you deal with CVEs and these staying audited and secure?
- mrmondo 10y agoWe use CentOS but PostgreSQL's official packages from their repo, just like we did when we were Debian based. http://yum.postgresql.org/ http://yum.postgresql.org/
- dboreham 10y agoWe use the official PG packages from their repo on CentOS. It appears there is an apt repository for Ubuntu too: https://www.postgresql.org/download/linux/ubuntu/ https://www.postgresql.org/download/linux/ubuntu/