On Fri, 11 Apr 2014 17:15:28 +0300 Achilleas Mantzios <achill@xxxxxxxxxxxxxxxxxxxxx> wrote: > pl/java has nothing to do with this. The argument against using > packages/ports for postgresql upgrades, is that upgrades in general > involve : > - reading HISTORY thoroughly and understanding every bit of it, > especially the migration part, and the changes part Do this before installing anything. > - backing up the current database Also this. > - installing the new binaries This is the only thing that the ports or pkgsrc (NetBSD) facility does for you. > - running pg_upgrade > - solving problems that pg_upgrade detects and trying again > - testing your in house C/Java/etc... functions > - testing your whole app + utilities against the new version After installing the upgrade all of this has to be done. None of it is going to be done by ports/pkgsrc/apt-get or any other install facility including your own brain sweat. All ports/pkgsrc does for you is the install part. > Now, tell me, how much of this can > the /usr/ports/databases/postgresqlXX-server port can do? Would you Step 3. Period. > trust the system to do this for you in an automated maybe weekly pkg > upgrade task that would handle e.g. cdrecord and postgresql-xxx in > the same manner ? I wouldn't trust any system to blindly install any program I certainly wouldn't automate any upgrades on a production server. The most I would do automatically is build the latest package for manual installation. > Now about writing ports, i can say to you this is a PITA. Its a great > concept, but you must truly commit to having a part of your life slot > maintaining the port you submitted. This could be fun at first, but > in the long run, this is not easy. Why? Once you submit your port to the community you could update when you could or poke the community to do it for you. All hail open source. -- D'Arcy J.M. Cain <darcy@xxxxxxxxx> | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 788 2246 (DoD#0082) (eNTP) | what's for dinner. IM: darcy@xxxxxxx, VoIP: sip:darcy@xxxxxxxxx -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
