RE: speeding up planning with partitions

From: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
To: "Imai, Yoshikazu" <imai(dot)yoshikazu(at)jp(dot)fujitsu(dot)com>, 'David Rowley' <david(dot)rowley(at)2ndquadrant(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: RE: speeding up planning with partitions
Date: 2019-01-22 05:58:52
Message-ID: 0A3221C70F24FB45833433255569204D1FB6CFCA@G01JPEXMBYT05
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


If the time for EXECUTE differs cleary before and after the creation of the generic plan, why don't you try to count the function calls for each EXECUTE? Although I haven't tried it, but you can probably do it with SystemTap, like this:

probe process("your_postgres_path").function("*").call {
/* accumulate the call count in an associative array */

Then, sort the functions by their call counts. You may find some notable difference between the 5th and 7th EXECUTE.

Takayuki Tsunakawa

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-01-22 06:07:30 Re: A few new options for vacuumdb
Previous Message Alexander Korotkov 2019-01-22 05:21:20 Re: jsonpath