Re: [PROPOSAL] VACUUM Progress Checker. - Mailing list pgsql-hackers

From Rahila Syed
Subject Re: [PROPOSAL] VACUUM Progress Checker.
Date
Msg-id CAH2L28tBVsvBCFdxhTS1POrQ6MbySH7tm2NsznjHRyAc-HzbMg@mail.gmail.com
Whole thread Raw
In response to Re: [PROPOSAL] VACUUM Progress Checker.  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: [PROPOSAL] VACUUM Progress Checker.
List pgsql-hackers

Hello,

While I am still looking at this WIP patch, I had one suggestion.

Instead of making changes in the index AM API can we have a call to update the shared state using pgstat_progress* API

directly from specific index level code?

Like  pgstat_count_index_scan(rel) call from _bt_first does. Though this function basically updates local structures and sends the count to stat collector via messages we can have a function which will instead modify the shared state using the progress API committed recently.

Thank you,

Rahila Syed

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Logical decoding slots can go backwards when used from SQL, docs are wrong
Next
From: Petr Jelinek
Date:
Subject: Re: Logical decoding slots can go backwards when used from SQL, docs are wrong