oddity in initdb probing of max_connections/shared_buffers

Поиск
Список
Период
Сортировка
От Greg Stark
Тема oddity in initdb probing of max_connections/shared_buffers
Дата
Msg-id CAM-w4HNch+7+jUvBQmasCR5h0B-rGS7TJFa6YnfHf4i3WyVrkw@mail.gmail.com
обсуждение исходный текст
Ответы Re: oddity in initdb probing of max_connections/shared_buffers  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
I happened to notice a bit of an inconsistency in the way initdb
probes max_connections and shared_buffers.

This line in the shared_buffers test:

/* Use same amount of memory, independent of BLCKSZ */
test_buffs = (trial_bufs[i] * 8192) / BLCKSZ;

has no equivalent in the max_connections test. As a result
max_connections is tested with 10 buffers per connection regardless of
BLCKSZ.

Is this intentional? Is the idea that Postgres can't function properly
without being able to read from 10 files concurrently regardless of
block size? Or is it an unintentional holdover from before the line
above was added for the shared_buffers tests?


-- 
greg



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

Предыдущее
От: Krzysztof Kaczkowski
Дата:
Сообщение: Re: Cluster on NAS and data center.
Следующее
От: Andrew Borodin
Дата:
Сообщение: Re: GiST optimizing memmoves in gistplacetopage for fixed-size updates [PoC]