anything one can do on the configuration side to
avoid such hash-join pitfalls?
Cheers,
Arturas
On Tue, Sep 28, 2021 at 4:13 PM Tom Lane wrote:
> Arturas Mazeika writes:
> > Thanks a lot for having a look at the query once again in more detail. In
> > short, you are right, I fire
I
Hi Michael,
Thanks a lot for having a look at the query once again in more detail. In
short, you are right, I fired the liquibase scripts and observed the exact
query that was hanging in pg_stats_activity. The query was:
SELECT
FK.TABLE_NAME as "TABLE_NAME"
, CU.COLUMN_NAM
Hi Michael,
Thanks for the answer.
I agree that the tables behind the views makes the query processing
challenging. What makes it even more challenging to us is that this query
is generated by a third party library that we use to operationalize the
schema changes.
I am trying to figure out what
