-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Might there be a way to tag those databases somehow so the backup
> script knows to skip them? I'd rather not hard code the list in
> the script.
Give them a unique connection limit, higher than max_connections,
e.g. ALTER DATABASE testdb
> What about using the comments on the database to control this?
That sounds close, though the comments are already being used for general
descriptions. I suppose it wouldn't hurt to add 'no_backup' to the
existing comments where appropriate. I was hoping maybe I'd missed a
'user-defined databas
On Nov 21, 2011, at 11:50, Mike Blackwell wrote:
> Might there be a way to
> tag those databases somehow so the backup script knows to skip them?
Add a table to each database that can be queried by the back up script to store
this additional metadata?
Michael Glaesemann
grzm seespotcode net
Mike Blackwell, 21.11.2011 17:50:
I've seen a couple backup scripts that query the metadata to
determine the list of databases to back up. I like this approach,
but have a few databases which don't get backed up for various
reasons, e.g. testing databases which we'd prefer to recreate on the
off
I've seen a couple backup scripts that query the metadata to determine the
list of databases to back up. I like this approach, but have a few
databases which don't get backed up for various reasons, e.g. testing
databases which we'd prefer to recreate on the off chance we loose them,
rather than h
