Your message dated Fri, 21 Nov 2014 19:07:27 +0100
with message-id <[email protected]>
and subject line Re: [Pkg-postgresql-public] Bug#770419: postgresql-9.4: 
Upgrade to 9.4~rc1-1 fails
has caused the Debian Bug report #770419,
regarding postgresql-9.4: Upgrade to 9.4~rc1-1 fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
770419: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770419
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: postgresql-9.4
Version: 9.4~rc1-1
Severity: grave
Justification: renders package unusable

This is addendum to bug #764705 and #768009. Opening a new report
since mail replying to update those is rejected "550 Unknown or
archived bug"


The instructions displayed by the current packages are still not working:

"
To resolve the situation, before upgrading, execute:
# su - postgres
$ pg_lsclusters
$ pg_ctlcluster 9.4 main start
$ pg_dumpall --cluster 9.4/main | gzip > 9.4-main.dump.gz
$ cp -a /etc/postgresql/9.4/main 9.4-main.config
$ pg_dropcluster 9.4 main --stop

Then after the upgrade, execute:
# su - postgres
$ pg_createcluster 9.4 main
$ cp 9.4-main.config/* /etc/postgresql/9.4/main
$ pg_ctlcluster 9.4 main start
$ zcat 9.4-main.dump.gz | psql -q --cluster 9.4/main
$ rm -rf 9.4-main.config 9.4-main.dump.gz
"

I followed them verbatim on a clean 'old' install and still
encountered this error:

$ zcat 9.4-main.dump.gz | psql -q --cluster 9.4/main
ERROR:  role "postgres" already exists

Manually decompressing the dump file and editing out the "CREATE ROLE
postgres;" was required for the final instructions to run successfully.

AYJ

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUbr7RAAoJELJo5wb/XPRjYNMH+QHXHF7gS9IExsI0M7X3/kfN
jNPwbKhkxOb4psGtQqdOt+jaXxukE4nuYRgeLGIY8hIZFRXIAL+B1qE9EefhYGin
1ZThes+B8xyxTCIPMhrrtfn8gVNLDkb1u0LuhojyhC3yo8NaJJ3LYFDgpx/hYMZK
Gexojsi/XmxyfLx0QyTllIEj0Zd2Od57mIj9oybEzt+cXyXuQUOJiITHcjU5t1p2
gHfQttsWoUU4cbBJQbF1rzz01dhI9+gVwxVMA5cKuo5BlHwwVoCmilpSQfXXY09g
7unklMeD7b9Rz/GxcBOqOyk2hGuutmg/rFZYeu5LU7LYE6/15mKzKd0AfabKrvA=
=JEcf
-----END PGP SIGNATURE-----

--- End Message ---
--- Begin Message ---
Re: Amos Jeffries 2014-11-21 <[email protected]>
> I followed them verbatim on a clean 'old' install and still
> encountered this error:
> 
> $ zcat 9.4-main.dump.gz | psql -q --cluster 9.4/main
> ERROR:  role "postgres" already exists
> 
> Manually decompressing the dump file and editing out the "CREATE ROLE
> postgres;" was required for the final instructions to run successfully.

This error is expected, it just means the "postgres" role is already
present in the target cluster. It is non-fatal, i.e. the rest of the
backup should have completed successfully.

Christoph
-- 
[email protected] | http://www.df7cb.de/

--- End Message ---
_______________________________________________
Pkg-postgresql-public mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public

Reply via email to