| From: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: New function to show index being vacuumed |
| Date: | 2023-06-22 16:22:17 |
| Message-ID: | 36F224E5-F419-42F9-A50F-AC8F01FE22B1@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I'm sorry for not having read (and not reading) the other thread yet,
> but what was the reason we couldn't store that oid in a column in the
> pg_s_p_vacuum-view?
> Could you summarize the other solutions that were considered for this issue?
Thanks for your feedback!
The reason we cannot stick the oid in pg_s_p_vacuum is because it will
not work for parallel vacuum as only the leader process has an entry
in pg_s_p_vacuum.
With a function the leader or worker pid can be passed in to the function
and will return the indexrelid being processed.
Regards,
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tommy Pavlicek | 2023-06-22 16:35:10 | [PATCH] Extend ALTER OPERATOR to support adding commutator, negator, hashes, and merges |
| Previous Message | Matthias van de Meent | 2023-06-22 15:55:27 | Re: New function to show index being vacuumed |