| From: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add index scan progress to pg_stat_progress_vacuum |
| Date: | 2022-03-10 01:37:58 |
| Message-ID: | 333D1326-1EED-416F-A9AF-21C90C1C098C@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > BTreeShmemInit();
> > SyncScanShmemInit();
> > AsyncShmemInit();
> > + vacuum_worker_init();
> > Don't we also need to add the size of the hash table to
> > CalculateShmemSize()?
> No, ShmemInitHash takes the min and max size of the hash and in turn calls ShmemInitStruct to setup the shared memory.
Sorry, I am wrong here. The size needs to be accounted for at startup.
--
Sami Imseih
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | houzj.fnst@fujitsu.com | 2022-03-10 02:17:32 | RE: Data is copied twice when specifying both child and parent table in publication |
| Previous Message | Imseih (AWS), Sami | 2022-03-10 01:22:37 | Re: Add index scan progress to pg_stat_progress_vacuum |