How can i monitor exactly what (partition) tables are accessed by a query? - Mailing list pgsql-general

From Robert Nix
Subject How can i monitor exactly what (partition) tables are accessed by a query?
Date
Msg-id CAC2EkfPNMxaFN2nQpRF-VeByks-Hh64Ev3JbmyFJ=EqAx+D9zw@mail.gmail.com
Whole thread Raw
Responses Re: How can i monitor exactly what (partition) tables are accessed by a query?  (Jov <amutu@amutu.com>)
Re: How can i monitor exactly what (partition) tables are accessed by a query?  (David G Johnston <david.g.johnston@gmail.com>)
List pgsql-general
I'm experiencing a problem with queries apparently not using the check constraints of my partition tables (tried constraint_exclusion =partition and =on with same results) and explain isn't sufficient to diagnose the issue because the value for the check constraint in the query comes from a join condition.

What i need is a way to see exactly what tables are actually accessed by the query.

When i hardcode the check constraint column's value into the query, the explain plan reports what i expect it should be executing but the performance of the query indicates that the partitions are not actually being used when the check constraint value is obtained from a join condition.

Any and all help appreciated.
--
.nix

pgsql-general by date:

Previous
From: John R Pierce
Date:
Subject: Re: Why isn't Java support part of Postgresql core?
Next
From: cowwoc
Date:
Subject: Re: Why isn't Java support part of Postgresql core?