Ummmm
Okee, this may be my setup being weird. I have been working on that
vacuum analyze bug and that may have killed something in the pg tables.
However, I am slightly concerned about this.
I am using 6.5.2 beta (the tarball on the ftp site)
-----------------------------
$ createdb games
% psql games
Welcome to the POSTGRESQL interactive sql monitor: Please read the file COPYRIGHT for copyright terms of POSTGRESQL
[PostgreSQL 6.5.1 on i586-pc-linux-gnu, compiled by gcc -ggdb ]
type \? for help on slash commands type \q to quit type \g or terminate with semicolon to execute queryYou are
currentlyconnected to the database: games
games=> create table game (
games-> refnum serial
games-> );
NOTICE: CREATE TABLE will create implicit sequence 'game_refnum_seq' for SERIAL column 'game.refnum'
NOTICE: CREATE TABLE/UNIQUE will create implicit index 'game_refnum_key' for table 'game'
pqReadData() -- backend closed the channel unexpectedly. This probably means the backend terminated abnormally
before or while processing the request.
We have lost the connection to the backend, so further processing is impossible. Terminating.
--------------------------------------------
Having top running when I do this, the backend eats all of my
available memory in about 5 seconds, before crashing or just aborting
when it has no memory left to alloacte.
Now, I have realised a mistake I made. I set my postmaster to run at:
/usr/bin/postmaster -d 30 -S -N 128 -B 256 -D/var/lib/pgsql/data > /tmp/postmasterout 2> /tmp/postmastererr
I set the debug to be -30 instead of its maximum of -3
Oops, it works now, but surely setting the debug level too high by
accident shouldnt cause a loop that eats everything in sight?
I have tested this switching the debug value to be 30 or 3 and in all
instances the 30 crashes it and the 3 does not. I am just concerned
that this may be an indication of a real problem that may notjust be
something that happens when the commandline args are set wrongly.
Just something that might bear looking into
~Michael