Re: Daniel Kahn Gillmor 2016-06-13 <87shwh6uyz@alice.fifthhorseman.net>
> fwiw, i used to do pg_upgradecluster as the postgres user on sysvinit
> machines, and it all worked fine. But of course the postgres user can't
> do that systemctl operations that a systemd machine needs, so
> pg_upgrade
On Fri 2016-06-10 20:29:55 -0400, peter green wrote:
> About a week ago I upgraded a server from wheezy to jessie. After the OS
> upgrade I upgraded from postgresql 9.1 to 9.4 using pg_updatecluster. It
> took a couple of attempts with pg_updatecluster to get things right
> (mainly because I was
Re: peter green 2016-06-11 <575b6f9a.5000...@p10link.net>
> On 11/06/16 01:29, peter green wrote:
> > How do I fix this? after some poking arround I discovered I could start
> > the server manually with "pg_ctlcluster 9.4 main start" but that is
> > obviously not a good long term soloution .
Start
On 11/06/16 01:29, peter green wrote:
How do I fix this? after some poking arround I discovered I could
start the server manually with "pg_ctlcluster 9.4 main start" but that
is obviously not a good long term soloution .
Ok, I solved it, doing the cluster upgrade multiple times had led to the
c
About a week ago I upgraded a server from wheezy to jessie. After the OS
upgrade I upgraded from postgresql 9.1 to 9.4 using pg_updatecluster. It
took a couple of attempts with pg_updatecluster to get things right
(mainly because I was using "debversion").
Today I ran a routine apt-get upgrade
