Postgres upgrade trouble

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: serge(dot)bourgeois(at)yahoo(dot)fr
Subject: Postgres upgrade trouble
Date: 2018-05-11 07:15:41
Message-ID: 152602294164.27210.4701522987280670267@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/static/pgupgrade.html
Description:

This is a non IT specialist question / comments. I like postgres, except the
current automatic upgrade mechanism working on my server...
On my Ubuntu 16.04 machine, when a postgres upgrade comes and installs
automatically, this creates a real nightmare: neither pgAdminIII not my
application can access the DB. (connection refused. Is the server running...
...on port 5432?)
Trying to understand in the documentation what to do is very difficult
because there is no clear example on how to retreive the 'old' or 'new'
parameters. So, I wonder why there is no automatic mechanism coming with the
upgrade to change the settings automatically, or alternatively to keep the
'old' version up and running correctly (and in this case the end user should
have an easy way to know that he has to launch an upgrade when he wants to,
and an utility -for instance in pgAdmin- should guide him along this upgrade
mechanism, ensuring I do not loose time nor any data).
Thanks for your efforts to offer Postgres to the IT community!

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Peter Korim 2018-05-11 12:46:37 documentation synopsis grammar
Previous Message David G. Johnston 2018-05-10 19:39:16 Re: Mistakes between an example and its description