From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: BTW, if anyone wants to work on it... |
Date: | 2005-05-03 10:55:15 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C73E5@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> 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/msg00001.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
Attachment | Content-Type | Size |
---|---|---|
patchpg.sh | application/octet-stream | 932 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= | 2005-05-03 13:00:22 | Regression tests |
Previous Message | Peter Eisentraut | 2005-05-03 10:46:18 | Re: [pgsql-advocacy] Increased company involvement |