-- Curt Sampson <cjs@cynic.net> wrote: > Some of your backends are getting pretty darn big. I wonder what > they're doing? It can't be sort memory at this point. But as you > can see, those five 200-250MB backends are killing you. no, not really: they use shared memory: >> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME COMMAND >> 6837 postgres 9 0 251M 251M 250M S 9.8 25.0 0:37 postmaster >> 6894 postgres 9 0 247M 247M 246M S 2.1 24.6 0:27 postmaster >> 6848 postgres 16 0 247M 247M 246M R 93.6 24.6 4:06 postmaster >> 6852 postgres 9 0 227M 227M 226M R 7.8 22.6 0:12 postmaster >> 6903 postgres 12 0 204M 204M 203M R 10.2 20.3 0:27 postmaster >> 6911 postgres 9 0 66840 65M 65728 S 19.4 6.4 0:01 postmaster >> 6845 postgres 9 0 52344 51M 50916 S 3.6 5.0 0:09 postmaster >> 6874 postgres 9 0 49408 48M 43168 S 19.8 4.7 3:57 postmaster >> 6875 postgres 11 0 41564 40M 35324 R 18.7 4.0 3:31 postmaster >> 6834 postgres 9 0 25456 24M 24356 S 3.0 2.4 0:26 postmaster >> 6889 postgres 9 0 24844 24M 23632 S 15.8 2.4 0:17 postmaster >> 6893 postgres 9 0 18396 17M 17332 S 0.1 1.7 0:07 postmaster [...] So it seems that some other processes eat the memory. Ciao Alvar -- // Unterschreiben! http://www.odem.org/informationsfreiheit/ // Internet am Telefon: http://www.teletrust.info/ // Das freieste Medium? http://www.odem.org/insert_coin/ // Blaster: http://www.assoziations-blaster.de/
pgsql-general by date:
Соглашаюсь с условиями обработки персональных данных