[arch-general] postgresql 9.3 -> 9.4

[Georg Altmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Looks like I hit quite a nail here. Let me describe my usecase. I was
doing this on my personal box. If it was on a production server, I
would have looked three times before doing an upgrade of any kind.
I would refrain from having a rolling release distro on a server
anyway, but that is another topic.
Probably I should have looked at the pacman output more closely. And
running a postgresql instance one should know that minor upgrades need
a dump and restore. I also think there are people with less experience
that are caught unprepared by such a situation. I know arch is for
experienced people, but what's the harm of showing a _pre_ upgrade
notice anyway?
In the end, a distribution and a packaging system should make life
easier not harder, right?
I humbly propose that for the next postgresql release that needs
manual intervention, there should be a _pre_ upgrade notice, clearly
saying that manual intervention is needed.

It doesn't look like pacman provides this capability though or does it?

Regards,
Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUyhJVAAoJELvxnEIeMg5lGMIIAIwLJSSiBuD5RduqZH9VkaYw
YdFhg+L5zVyR3QPx1Hw3F4l0xS5QoGvQG3aZiF14lQhvf4ANlkLahJpZBMa4MRpM
eZzJVpSNTNiLDXqpycxn1dD8N2yjvrT4j7Qa/dmropArHdWn14Xy8lg4Q1lBW2vN
heLSZgIKL90vd+I3bJFOCxoU92w5tzn9L65Wl3qxW/exLcka/VMVXknp5NOMD0tb
0xXB615r9IOzcMgfaxRDMcuzx5doBS/e/ICNlShG52ZcAPmhCBVAfeHzwQRIIerT
D+DCCHl1HQTgzPBIcfxmerlOTmIN4ZWbjIS0Tyj36QFqD2Zv5xYwfa+znOEExDQ=
=TNjm
-----END PGP SIGNATURE-----