Re: New function to show index being vacuumed - Mailing list pgsql-hackers

From Imseih (AWS), Sami
Subject Re: New function to show index being vacuumed
Date
Msg-id 36F224E5-F419-42F9-A50F-AC8F01FE22B1@amazon.com
Whole thread Raw
In response to Re: New function to show index being vacuumed  (Matthias van de Meent <boekewurm+postgres@gmail.com>)
List 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







pgsql-hackers by date:

Previous
From: Matthias van de Meent
Date:
Subject: Re: New function to show index being vacuumed
Next
From: Tommy Pavlicek
Date:
Subject: [PATCH] Extend ALTER OPERATOR to support adding commutator, negator, hashes, and merges