From: | Jim Mercer <jim(at)reptiles(dot)org> |
---|---|
To: | Mark Jewiss <Mark(dot)Jewiss(at)knowledge(dot)com> |
Cc: | pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] Cleaning up vacuums |
Date: | 1999-11-24 14:42:37 |
Message-ID: | 19991124094236.O17675@reptiles.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Nov 24, 1999 at 02:25:11PM +0000, Mark Jewiss wrote:
> Each time I vacuum (from either the script or the command line), I see
> things like:
>
> DEBUG: --Relation pg_indexes--
> DEBUG: Pages 0: Changed 0, Reapped 0, Empty 0, New 0; Tup 0: Vac 0,
> Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 0, MaxLen 0; Re-using: Free/Avail.
> Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
>
> Redirecting STDERR or STDOUT somewhere doesn't seem to have any effect on
> these messages.
>
> Any ideas anyone?
must be something in your perl script.
i do similar things using /bin/sh scripts as:
psql -h host -d database -c "vacuum verbose;" > errors 2>&1
if [ $? -ne 0 ] ; then
Mail -s "vacuum errors" someone < errors
fi
rm -f errors
works fine.
also, if you enable syslog (include/config.h) and set up a pg_options file,
i've noticed that verbose level 2 will put the output of vacuum into
the syslog file.
--
[ Jim Mercer jim(at)reptiles(dot)org +1 416 506-0654 ]
[ Reptilian Research -- Longer Life through Colder Blood ]
[ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ]
From | Date | Subject | |
---|---|---|---|
Next Message | Wim van den Berge | 1999-11-24 15:28:14 | Re: [NOVICE] Re: [GENERAL] Re: Is PostgreSQL ready for mission criticalapplications? |
Previous Message | Mark Jewiss | 1999-11-24 14:25:11 | Cleaning up vacuums |