Kurt Roeckx wrote:
Hi,
This is a harmless warning, and it should just fall back to using
ipv4 instead. I suspect there is some other error, but have to
wonder why it's not showing up in the log.
Could you maybe do a strace -f -F of it, and see what happens?
Kurt
Solved using current etch version of pgsql. I agree with you, it wasn't
the IPv6 error, since turning off ip socket binding in postmaster.conf
did nothing. I tried starting Postgres with pg_ctl, postmaster and the
utilities in bin/ directory.
Definitely, PostgreSQL wasn't logging anywhere. I doublechecked access
times and synced, but nothing happened. This was an upgraded version of
PostgreSQL from Woody in an Alphaserver DS20.
Following are 33 lines of what I think is a phantom logging from
PostgreSQL, since access time to the file which I took it from was
coherent with the test times:
stmmarce7_idx: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
stmmarce6_idx: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
stmmarce5_idx: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
stmmarce4_idx: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
stmmarce3_idx: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
stmmarce2_idx: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
stmmarce1_idx: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
pg_index_indrelid_index: 1024 total in 1 blocks; 640 free (0 chunks);
384 used
pg_operator_oprname_l_r_k_index: 2096 total in 2 blocks; 816 free (0
chunks); 1280 used
pg_type_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
pg_proc_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
pg_proc_proname_narg_type_index: 2096 total in 2 blocks; 816 free (0
chunks); 1280 used
pg_amop_opc_strategy_index: 1024 total in 1 blocks; 352 free (0 chunks);
672 used
pg_operator_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
pg_amproc_opc_procnum_index: 1024 total in 1 blocks; 352 free (0
chunks); 672 used
pg_shadow_usename_index: 1024 total in 1 blocks; 640 free (0 chunks);
384 used
pg_index_indexrelid_index: 1024 total in 1 blocks; 640 free (0 chunks);
384 used
pg_trigger_tgrelid_index: 1024 total in 1 blocks; 640 free (0 chunks);
384 used
pg_class_oid_index: 1024 total in 1 blocks; 640 free (0 chunks); 384 used
pg_class_relname_index: 1024 total in 1 blocks; 640 free (0 chunks); 384
used
pg_attribute_relid_attnum_index: 1024 total in 1 blocks; 352 free (0
chunks); 672 used
MdSmgr: 8192 total in 1 blocks; 4048 free (0 chunks); 4144 used
DynaHash: 8192 total in 1 blocks; 5856 free (0 chunks); 2336 used
DynaHashTable: 8192 total in 1 blocks; 4032 free (0 chunks); 4160 used
DynaHashTable: 24576 total in 2 blocks; 16240 free (4 chunks); 8336 used
DynaHashTable: 24576 total in 2 blocks; 16240 free (4 chunks); 8336 used
DynaHashTable: 24576 total in 2 blocks; 14192 free (5 chunks); 10384 used
DPGSTAT: cannot open temp stats file
PGSTAT: /sapidata/data/global/pgstat.tmp.12172: No such file or directory
Found a pre-existing shared memory block (ID 386816) still in use.
If you're sure there are no old backends still running,
remove the shared memory block with ipcrm(1), or just
delete "/sapidata/data/postmaster.pid".
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
