Re: Query plan changes after pg_dump / pg_restore
От
Christopher Kings-Lynne
Тема
Re: Query plan changes after pg_dump / pg_restore
Дата
Msg-id
42A7FD12.2080608@familyhealth.com.au
Ответ на
Список
Дерево обсуждения
Query plan changes after pg_dump / pg_restore jonanews@oismail.com
Re: Query plan changes after pg_dump / pg_restore Dennis Bjorklund <db@zigo.dhs.org>
Re: Query plan changes after pg_dump / pg_restore Jona <jonanews@oismail.com>
Re: Query plan changes after pg_dump / pg_restore Tom Lane <tgl@sss.pgh.pa.us>
Re: Query plan changes after pg_dump / pg_restore Jona <jonanews@oismail.com>
Re: Query plan changes after pg_dump / pg_restore Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: Query plan changes after pg_dump / pg_restore Jona <jonanews@oismail.com>
Re: Query plan changes after pg_dump / pg_restore Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: Query plan changes after pg_dump / pg_restore Jona <jonanews@oismail.com>
Re: Query plan changes after pg_dump / pg_restore Dennis Bjorklund <db@zigo.dhs.org>
Re: Query plan changes after pg_dump / pg_restore Jona <jonanews@oismail.com>
> Thank you for the swift reply, the following is the output of the SHOW > ALL for shared_buffers and effective_cache_size. > shared_buffers: 13384 > effective_cache_size: 4000 > server memory: 2GB effective_cache_size should be 10-100x larger perhaps... Chris
В списке pgsql-performance по дате отправления