| From: | Rahila Syed <rahilasyed90(at)gmail(dot)com> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, pokurev(at)pm(dot)nttdata(dot)co(dot)jp, bannos(at)nttdata(dot)co(dot)jp |
| Subject: | Re: [PROPOSAL] VACUUM Progress Checker. |
| Date: | 2016-03-14 09:55:17 |
| Message-ID: | CAH2L28tBVsvBCFdxhTS1POrQ6MbySH7tm2NsznjHRyAc-HzbMg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2016-03-14 09:56:06 | Re: Logical decoding slots can go backwards when used from SQL, docs are wrong |
| Previous Message | Craig Ringer | 2016-03-14 09:48:14 | Re: Logical decoding slots can go backwards when used from SQL, docs are wrong |