While both suggestions should work, I'd like another.
Locking each table one-by-one could be done, but some of these
databases are kept current by sliding unique (and arbitrarily) named
tables under a view with a fixed named that www selects from. Of
course, I could generate a list of all tab
try this:
begin;
lock ;
...
end;
In the meantime, while you locked every table in your database with
locks, and before "end" or "commit" or "rollback", no user can
read/write none of your tables. You can delete temporary files,
and then restore database functionality.
It should word in 6.4.2,
Does anyone know a way to lock a database under postgres while
leaving available the other databases managed by postmaster?
We are running postgreSQL 6.4.2 on our web site for content serving
and for registration information. There are 4 separate databases
served by postmatser to support these
