Colm

The fix for #6293 _Add citus.skip_advisory_lock_permission_checks_ provides a workaround for this issue; set `citus.skip_advisory_lock_permission_checks` to on. As noted there, _While dealing with replicated tables, Citus acquires some locks that Postgres...

@xrossdata thanks for reporting. This looks like an execution-time problem, as the query runs ok on empty tables (below). Can you provide some INSERTs that help in reproducing ? We...

Thanks @xrossdata we were able to reproduce the issue with this information. The problem is caused by Citus not handling an optimization that Postgres 17 applies to the window clause...

It looks like the problem may be caused by a dangling pointer; debugging the Postgres planner shows that optimization [c651020 ](https://github.com/postgres/postgres/commit/c65102006b686ea26194fb539d7a416a089300e0) is applied to the windows clause, so that it...

A couple of observations that may aid in resolving this; using @naisila 's simpler query, the crash occurs in `get_sublink_expr()`: ``` foreach(l, ((BoolExpr *) sublink->testexpr)->args) { OpExpr *opexpr = lfirst_node(OpExpr,...

@imranzaheer612 thanks for the diagnosis, it makes total sense. Does `UPDATE` have the same issue do you know, or it is just impacting `DELETE` ? _deparsing here is done on...

Thanks for reporting this @upmanish . Have you encountered the issue with other Citus versions? _Note: Can provide SQL and schema along with logs privately if needed._ Yes, knowing the...

Thanks @upmanish this will really help in reproducing. One other detail - how many nodes in your Citus cluster ?

This looks like a bug in `INSERT .. SELECT` planning, specifically for schema-sharded and reference tables when the SELECT has a GROUP BY. If `GROUP BY` is removed, the query...

Thanks for submitting this @imranzaheer612 , it looks like it fixes the issue. There's a couple of minor details: - Need to run `ci/editorconfig.sh` from your branch's root dir to...