| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(dot)com>, Antonin Houska <ah(at)cybertec(dot)at> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Conflicting updates of command progress |
| Date: | 2025-04-15 07:07:07 |
| Message-ID: | ad3ded83-532e-4c4f-8108-344924c47db0@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2025-04-15 07:07:49 | Re: pg_dump --if-exists --clean when drop index that is partition of a partitioned index |
| Previous Message | jian he | 2025-04-15 06:51:48 | Re: pg_dump --if-exists --clean when drop index that is partition of a partitioned index |