On Sun, Aug 13, 2000 at 10:23:41AM -0400, Brian Schramm wrote
> I just got through installing Potato on my HP Pavilion 133 computer with
> 80 meg of ram and a 8gig HD.
>
> When I come back to it from letting it sit idle for about 8 hours this is
> on the tty1 screen:
>
> 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.
> DEBUG:
> --Relation pg_rewrite--
> DEBUG: Pages 3: Changed 0, Reapped 0, Empty 0, New 0; Tup 5:
> Vac 0, Keep/VTL 0/0, Crash 0, UnUsed 0, MinLen 2568, MaxLen 4609;
> Re-using: Free/Avail. Space 0/0; EndEmpty/Avail. Pages 0/0. Elapsed 0/0
> sec.
> DEBUG:
[snip]
I'm now running the 'woody' version of Postgresql, and on my setup
this is fixed by setting
PGDEBUG=0
(or, for that matter, PGDEBUG=anything).
If PGDEBUG or PGECHO are set the Postmaster's output is redirected
to a log file, whereas if they aren't then the output is not so
redirected, presumably in the mistaken belief that if you don't
set those options then no output is produced.
The "offending" code is in /usr/lib/postgresql/bin/postgresql-startup,
which on my system includes this chunk starting at line 232:
# Ready to go: stand clear...
echo Starting PostgreSQL postmaster
cd ${POSTGRES_HOME}
if [ -n "${DEBUGLEVEL}" -o "${PGECHO}" = yes ]
then
touch ${POSTGRES_LOG:=/var/log/postgres.log}
chown postgres.postgres ${POSTGRES_LOG}
chmod 660 ${POSTGRES_LOG}
su postgres -c "${POSTMASTER} -b ${POSTGRES} ${BUFFERS} ${BACKENDOPT} \
-D ${PGDATA} ${DEBUGLEVEL} ${TCP} ${PORT} ${OPTIONS} \
>> ${POSTGRES_LOG} 2>&1 &"
else
su postgres -c "${POSTMASTER} -b ${POSTGRES} ${BUFFERS} ${BACKENDOPT} \
-D ${PGDATA} ${TCP} ${PORT} ${OPTIONS} &"
fi
HTH,
John P.
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.mdt.net.au/~john Debian Linux admin & support:technical services
