Ping Yao writes:
> Thank you for the comment. I think we do. What I found odd here is the
> Query Plan (with analyze) clearly shows the actual execution to be very
> quick, that's why I don't think it's an index problem. What do you think?
I wouldn't rule it out on that basis. Foreign key enforc
On Mon, Dec 4, 2023 at 3:43 PM Ping Yao wrote:
>
> Hi Merlin,
>
> Thank you for the comment. I think we do. What I found odd here is the
> Query Plan (with analyze) clearly shows the actual execution to be very
> quick, that's why I don't think it's an index problem. What do you think?
>
I'm not
Hi Merlin,
Thank you for the comment. I think we do. What I found odd here is the
Query Plan (with analyze) clearly shows the actual execution to be very
quick, that's why I don't think it's an index problem. What do you think?
Ping
--
Pook-Ping Yao (He/Him)
Chief Technology Officer and co-Fou
On Fri, Dec 1, 2023 at 11:48 AM Ping Yao wrote:
> Hello All.
>
> First timer here, long time user though. Thank you in advance.
>
> Can someone help me understand why my simple DELETE query is so slow to
> run?
>
Not familiar with citus to diagnose any citus issues. Having said that,
can you co
> On Dec 1, 2023, at 09:47, Ping Yao wrote:
> Can someone help me understand why my simple DELETE query is so slow to run?
Based on the plan, you're running PostgreSQL with the Citus extension, and the
delay is in Citus-related code. This is probably a question best directed to
either the o
Hello All.
First timer here, long time user though. Thank you in advance.
Can someone help me understand why my simple DELETE query is so slow to run?
*System:*
We are running Citus with 4 workers with 256 shards (default), with
replication using pg_autoctl.
*PostgreSQL Version:*
=# select
