Re: Seeing execution plan of foreign key constraint check?
От | Jim Nasby |
---|---|
Тема | Re: Seeing execution plan of foreign key constraint check? |
Дата | |
Msg-id | c693bae7-1779-d7f7-5485-2578974b02b9@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: Seeing execution plan of foreign key constraint check? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Seeing execution plan of foreign key constraint check?
|
Список | pgsql-performance |
On 7/19/16 3:10 PM, Tom Lane wrote: > Jim Nasby <Jim.Nasby@BlueTreble.com> writes: >> On 7/5/16 7:14 AM, Robert Klemme wrote: >>> I was wondering whether there are any plans to include the plan of the >>> FK check in EXPLAIN output. Or is there a different way to get to see >>> all the plans of triggers as well as of the main SQL? > >> Unfortunately, this isn't the type of thing that would excite most of >> the core hackers, so it's unlikely any of them will pick this up. > > It's not so much that people don't care, as that it's not apparent how to > improve this without breaking desirable system properties --- in this > case, that functions are black boxes so far as callers are concerned. I thought we already broke out time spent in triggers as part of EXPLAIN, and that the FK "triggers" were specifically ignored? (Granted, that doesn't give you plan info, just timing...) As for function plans, ISTM that could be added to the PL handlers if we wanted to (allow a function invocation to return an array of explain outputs). -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532) mobile: 512-569-9461
В списке pgsql-performance по дате отправления: