Skip site navigation (1) Skip section navigation (2)

Re: Heavy postgres process

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Guido Barosio" <gbarosio(at)gmail(dot)com>
Cc: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>, "Kenneth Marshall" <ktm(at)rice(dot)edu>, Vivek_Sharan <Vivek_Sharan(at)infosys(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Heavy postgres process
Date: 2008-09-17 21:38:49
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
"Guido Barosio" <gbarosio(at)gmail(dot)com> writes:
> Getting to the latest 7.4 server involves the same as going to the
> latest 8.x server, AFAIK, if we take in consideration that 7.4.8
> requires a dump & restore (meaning downtime).

(a) it does *not* require a dump and restore

(b) if you ignore the recommendations in the 7.4.8 notes and just
upgrade without doing anything else, then what you will have is a
7.4 system that still contains two security vulnerabilities.
Vulnerabilities that are in your 7.4.5 system today.  How are you
worse off?

This is about the lamest excuse for not updating I've ever heard.

			regards, tom lane

In response to

pgsql-admin by date

Next:From: Melissa PetersonDate: 2008-09-17 21:41:13
Subject: Re: unable to backup database -- psql not up to date
Previous:From: Tom LaneDate: 2008-09-17 21:33:27
Subject: Re: unable to backup database -- psql not up to date

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group