Message-ID: <ad3ded83-532e-4c4f-8108-344924c47db0@oss.nttdata.com>
Date: Tue, 15 Apr 2025 16:07:07 +0900
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Conflicting updates of command progress
To: Sami Imseih <samimseih@gmail.com>, Antonin Houska <ah@cybertec.at>
Cc: pgsql-hackers@postgresql.org
References: <117147.1744380740@localhost>
 <CAA5RZ0s_Hta6PWDwY9Lf-c+14F+C13BK2ax=B6R7bmDNhN6xdQ@mail.gmail.com>
Content-Language: en-US
From: Fujii Masao <masao.fujii@oss.nttdata.com>
In-Reply-To: <CAA5RZ0s_Hta6PWDwY9Lf-c+14F+C13BK2ax=B6R7bmDNhN6xdQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/ad3ded83-532e-4c4f-8108-344924c47db0%40oss.nttdata.com>
Precedence: bulk


On 2025/04/15 2:13, Sami Imseih wrote:
>> While working on [1] I realized that some field of pg_stat_progress_cluste has
>> weird value.

I ran into the same issue while working on [2], and eventually had to
withdraw that patch because of it.


> Is there a repro that you can share that shows the weird values? It sounds like
> the repro is on top of [1]. Is that right?

You can reproduce the similar problem by creating a trigger function that
runs a progress-reporting command like COPY, and then COPY data into
a table that uses that trigger.

Regards,

[2] https://commitfest.postgresql.org/patch/5282/

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION