Hi,
> Hm. I cannot see anything wrong with the source code for database_size.
> I notice though that it depends on vsnprintf, which is known to be buggy
> in some releases of Solaris. Did you use the patch suggested in the
> last entry of doc/FAQ_Solaris?
>
I can't find any infos about patches in the FAQ
bash-2.03# grep -i patch FAQ_Solaris
> > This started to happen when I increased memory sizes in the
> > postgresql.conf.
>
> From what, to what?
>
> regards, tom lane
ok. first of all. here are the entries from /etc/system
set shmsys:shminfo_shmmax=1073741824
set semsys:seminfo_semmap=64
set semsys:seminfo_semmni=4096
set semsys:seminfo_semmns=4096
set semsys:seminfo_semmnu=4096
set semsys:seminfo_semume=64
set semsys:seminfo_semmsl=100
set shmsys:shminfo_shmmin=100
set shmsys:shminfo_shmmni=100
set shmsys:shminfo_shmseg=100
and the entries from postgresql.conf. values where changed from default.
shared_buffers = 1024 # 2*max_connections, min 16, typically 8KB
each
max_fsm_relations = 100 # min 10, fsm is free space map, ~40 bytes
max_fsm_pages = 10000 # min 1000, fsm is free space map, ~6 bytes
max_locks_per_transaction = 128 # min 10
wal_buffers = 64 # min 4, typically 8KB each
sort_mem = 65536 # min 64, size in KB
vacuum_mem = 65536 # min 1024, size in KB
checkpoint_segments = 3 # in logfile segments, min 1, 16MB each
checkpoint_timeout = 300 # range 30-3600, in seconds
#
commit_delay = 0 # range 0-100000, in microseconds
commit_siblings = 5 # range 1-1000
#
fsync = true
wal_sync_method = fsync # the default varies across platforms:
# # fsync, fdatasync, open_sync, or
open_datasync
wal_debug = 0 # range 0-16
regards
-andreas
--
Andreas Schmitz - Phone +49 201 8501 318
Cityweb-Technik-Service-Gesellschaft mbH
Friedrichstr. 12 - Fax +49 201 8501 104
45128 Essen - email a.schmitz@cityweb.de