| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Josef Šimánek <josef(dot)simanek(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Subject: | Re: Improvements and additions to COPY progress reporting |
| Date: | 2021-02-20 23:23:02 |
| Message-ID: | YDGZ1jnuwdjEn+4P@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Feb 20, 2021 at 02:29:44PM +0530, Bharath Rupireddy wrote:
> Yeah. We could use pgstat_progress_update_multi_param instead of
> pgstat_progress_update_param to update multiple params.
>
> On a quick scan through the code, I found that we can do the following. If
> okay, I can start a new thread so that we don't divert the main thread
> here. Thoughts?
Having a separate thread to discuss this part would be right. This
way any patches sent would attract the correct audience.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2021-02-20 23:31:39 | Re: Some regular-expression performance hacking |
| Previous Message | Michael Paquier | 2021-02-20 23:18:38 | Re: some pointless HeapTupleHeaderIndicatesMovedPartitions calls |