Re: poor pefrormance with regexp searches on large tables
От | Kevin Grittner |
---|---|
Тема | Re: poor pefrormance with regexp searches on large tables |
Дата | |
Msg-id | 4E425D2D020000250003FD32@gw.wicourts.gov обсуждение исходный текст |
Ответ на | poor pefrormance with regexp searches on large tables (Grzegorz Blinowski <g.blinowski@gmail.com>) |
Ответы |
Re: poor pefrormance with regexp searches on large tables
|
Список | pgsql-performance |
Grzegorz Blinowski <g.blinowski@gmail.com> wrote: > Some performance params from postgresql.conf: Please paste the result of running the query on this page: http://wiki.postgresql.org/wiki/Server_Configuration For a start, the general advice is usually to start with shared_buffers at the lesser of 25% of system RAM or 8 GB, and adjust from there based on benchmarks. So you might want to try 4GB for that one. Just to confirm, you are using 2 Phase Commit? (People sometimes mistake the max_prepared_transactions setting for something related to prepared statements.) I concur with previous advice that using one regular expression which matches all of the terms is going to be a lot faster than matching each small regular expression separately and then combining them. -Kevin
В списке pgsql-performance по дате отправления: