Re: bug: copy progress reporting of backends which run multiple COPYs
От | Justin Pryzby |
---|---|
Тема | Re: bug: copy progress reporting of backends which run multiple COPYs |
Дата | |
Msg-id | ZjoeSq3mgYpl6Dhj@pryzbyj2023 обсуждение исходный текст |
Ответ на | Re: bug: copy progress reporting of backends which run multiple COPYs (Matthias van de Meent <boekewurm+postgres@gmail.com>) |
Ответы |
Re: bug: copy progress reporting of backends which run multiple COPYs
|
Список | pgsql-hackers |
On Sat, Jan 21, 2023 at 02:45:40AM +0100, Matthias van de Meent wrote: > > Would you do anything different in the master branch, with no > > compatibility constraints ? I think the progress reporting would still > > be limited to one row per backend, not one per CopyFrom(). > > I think I would at least introduce another parameter to BeginCopyFrom > for progress reporting (instead of relying on pstate != NULL), like > how we have a bit in reindex_index's params->options that specifies > whether we want progress reporting (which is unset for parallel > workers iirc). This didn't get fixed for v16, and it seems unlikely that it'll be addressed in back branches. But while I was reviewing forgotten threads, it occurred to me to raise the issue in time to fix it for v17. -- Justin
В списке pgsql-hackers по дате отправления: