Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql-server/ oc/src/sgml/manage-ag.sgml oc/sr ...

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql-server/ oc/src/sgml/manage-ag.sgml oc/sr ...
Date: 2003-03-21 17:05:36
Message-ID: Pine.LNX.4.44.0303211443380.2387-100000@peter.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackers
Tom Lane writes:

> > for d in $(psql -l --somthing); do vacuum $d; done
> If you have a real shell (and know how to use it), sure.  Is such a
> solution acceptable to all those Windows users we're hoping to attract?

I don't know how Windows users typically manage their systems, but if they
use batch files they can also write a similar loop with the native shell.
(I just tried it.)

My problem with a program that runs a command for all databases is that it
is too rigid:  What if you want to run maintenance only on some databases
(owned by you, big/small, even/odd, starting with 'x')?  --- Cannot use
it, back to the manual approach.

Peter Eisentraut   peter_e(at)gmx(dot)net

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2003-03-21 17:12:22
Subject: Re: cursors: SCROLL default, error messages
Previous:From: Peter EisentrautDate: 2003-03-21 17:03:27
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign

pgsql-committers by date

Next:From: Bruce Momjian - CVSDate: 2003-03-21 17:11:46
Subject: pgsql-server/doc/src/sgml/ref declare.sgml
Previous:From: Bruce Momjian - CVSDate: 2003-03-21 15:43:02
Subject: pgsql-server/src/backend/commands tablecmds.c

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group