Re: [HACKERS] BTW, if anyone wants to work on it...
On Tue, 03 May 2005 02:45:09 -0400, Tom Lane <[EMAIL PROTECTED]> wrote:
> I'm starting to think
>it'd be worth setting up a mechanism to handle such changes
>automatically.
I've been using this skeleton for quite some time now. Magnus'
psql ... | while read D
might be more robust than my
for db in `enumdatabases`
Servus
Manfred
#!/bin/sh
#---
# pg_plug -- painless upgrade
# PG 7.4 standard -> PG 7.4 with various enhancements
#
# 2003-10-04 mk new
# 2003-10-14 mk addpatchinfo
# 2003-11-01 mk VIEW pg_patchinfo
# 2004-11-04 mk renamed VIEW to pg_patches;
# features selectable via command line (-F)
# 2004-12-14 mk freeze
#---
ALLFEATURES="22 27"
#---
abortscript(){
echo 1>&2
echo "$1" 1>&2
exit 1
}
setconnectable(){
db=$1
allow=$2
$CMD template1 >/dev/null
Re: [HACKERS] BTW, if anyone wants to work on it...
> We've had a couple of cases recently where we had to advise > DBAs to make manual changes in the system catalogs --- see > for instance the 7.4.2 release notes or > http://archives.postgresql.org/pgsql-announce/2005-05/msg1.php > > It'd be nicer if this sort of thing could be handled > automatically by a software update. There are good reasons > why it's not trivial, but having been burnt twice in recent > memory, I'm starting to think it'd be worth setting up a > mechanism to handle such changes automatically. Anyone up > for working on it? I suppose you want something a bit less trivial than this one, but if somebody has benefit from it, here's the script I've been using to patch my dbs. It's very trivial - error checking is dba-eyeballs, for example. But if there are lots of databases, at least it saves a few steps. A more complete solution would of course require some better error checking ;-) //Magnus patchpg.sh Description: patchpg.sh ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[HACKERS] BTW, if anyone wants to work on it...
We've had a couple of cases recently where we had to advise DBAs to make manual changes in the system catalogs --- see for instance the 7.4.2 release notes or http://archives.postgresql.org/pgsql-announce/2005-05/msg1.php It'd be nicer if this sort of thing could be handled automatically by a software update. There are good reasons why it's not trivial, but having been burnt twice in recent memory, I'm starting to think it'd be worth setting up a mechanism to handle such changes automatically. Anyone up for working on it? regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
