Re: Speed up transaction completion faster after many relations areaccessed in a transaction
От | Tomas Vondra |
---|---|
Тема | Re: Speed up transaction completion faster after many relations areaccessed in a transaction |
Дата | |
Msg-id | 8cd83f8e-6bd2-5782-2a8f-ecbeb9d1eb86@2ndquadrant.com обсуждение исходный текст |
Ответ на | Speed up transaction completion faster after many relations areaccessed in a transaction ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>) |
Ответы |
RE: Speed up transaction completion faster after many relations areaccessed in a transaction
|
Список | pgsql-hackers |
On 2/12/19 7:33 AM, Tsunakawa, Takayuki wrote: > ... > > This problem was uncovered while evaluating partitioning performance. > When the application PREPAREs a statement once and then > EXECUTE-COMMIT repeatedly, the server creates a generic plan on the > 6th EXECUTE. Unfortunately, creation of the generic plan of > UPDATE/DELETE currently accesses all partitions of the target table > (this itself needs improvement), expanding the LOCALLOCK hash table. > As a result, 7th and later EXECUTEs get slower. > > Imai-san confirmed performance improvement with this patch: > > https://commitfest.postgresql.org/22/1993/ > Can you quantify the effects? That is, how much slower/faster does it get? regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: