Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception

Поиск
Список
Период
Сортировка
От Craig James
Тема Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Дата
Msg-id 48CE7076.1040309@emolecules.com
обсуждение исходный текст
Ответ на Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception  (Florian Weimer <fweimer@bfk.de>)
Список pgsql-performance
Florian Weimer wrote:
> * Craig James:
>
>>> There are some run-time environments which allocate huge chunks of
>>> memory on startup, without marking them as not yet in use.  SBCL is in
>>> this category, and also the Hotspot VM (at least some extent).
>> I stand by my assertion: It never makes sense.  Do these
>> applications allocate a terrabyte of memory?  I doubt it.
>
> SBCL sizes its allocated memory region based on the total amount of
> RAM and swap space.  In this case, buying larger disks does not
> help. 8-P

SBCL, as Steel Bank Common Lisp? Why would you run that on a server machine alongside Postgres? If I had to use SBLC
andPostgres, I'd put SBLC on a separate machine all its own, so that it couldn't corrupt Postgres or other servers that
hadto be reliable. 

Are you saying that if I bought a terrabyte of swap disk, SBLC would allocate a terrabyte of space?

Craig


В списке pgsql-performance по дате отправления:

Предыдущее
От: Florian Weimer
Дата:
Сообщение: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Следующее
От: Matthew Wakeling
Дата:
Сообщение: Re: Effects of setting linux block device readahead size