From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
---|---|
To: | torikoshia <torikoshia(at)oss(dot)nttdata(dot)com>, Rafael Thofehrn Castro <rafaelthca(at)gmail(dot)com>, robertmhaas(at)gmail(dot)com |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: Progressive explain |
Date: | 2025-03-31 06:24:26 |
Message-ID: | ef71c2b7-dd1c-4321-b223-09c4efbfc3ae@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2025-03-31 06:28:29 | PRI?64 vs Visual Studio (2022) |
Previous Message | Yugo Nagata | 2025-03-31 06:24:15 | Improve coments on structures in trigger.c |