Re: Proposal: Progressive explain - Mailing list pgsql-hackers

From Andrei Lepikhov
Subject Re: Proposal: Progressive explain
Date
Msg-id ef71c2b7-dd1c-4321-b223-09c4efbfc3ae@gmail.com
Whole thread Raw
In response to Re: Proposal: Progressive explain  (torikoshia <torikoshia@oss.nttdata.com>)
List pgsql-hackers
On 3/31/25 02:23, torikoshia wrote:
> On Fri, Mar 7, 2025 at 6:43 AM Rafael Thofehrn Castro 
>> Implemented this version. New patch has the following characteristics:
> 
> 
> I haven't looked into the code yet, but when I ran below commands during 
> make installcheck, there was an error and an assertion failure
> 
>    =# select * from pg_stat_progress_explain;
>    =# \watch 0.1
Yeah, that's to be expected.
I think many corner cases may be found: hash table in the middle of 
filling, opened file descriptors, an incorrect combination of variables, 
  'not yet visited' subtrees - who knows what else? So, last time, I 
just ended up with the idea that using the explain code is a bit 
dangerous - in the middle of execution, it is enough to expose only 
basic data - rows, numbers and timings. It seems safe to gather.

-- 
regards, Andrei Lepikhov



pgsql-hackers by date:

Previous
From: Yugo Nagata
Date:
Subject: Improve coments on structures in trigger.c
Next
From: Kyotaro Horiguchi
Date:
Subject: PRI?64 vs Visual Studio (2022)