Re: GenBKI emits useless open;close for catalogs without rows
От | Heikki Linnakangas |
---|---|
Тема | Re: GenBKI emits useless open;close for catalogs without rows |
Дата | |
Msg-id | 286e368f-b884-8cfa-5c5a-22a743c6dd25@iki.fi обсуждение исходный текст |
Ответ на | Re: GenBKI emits useless open;close for catalogs without rows (Matthias van de Meent <boekewurm+postgres@gmail.com>) |
Ответы |
Re: GenBKI emits useless open;close for catalogs without rows
Re: GenBKI emits useless open;close for catalogs without rows Re: GenBKI emits useless open;close for catalogs without rows |
Список | pgsql-hackers |
On 18/09/2023 17:50, Matthias van de Meent wrote: > (initdb takes about 73ms locally with syncing disabled) That's impressive. It takes about 600 ms on my laptop. Of which about 140 ms goes into processing the BKI file. And that's with "initdb -no-sync" option. > Various methods of reducing the size of postgres.bki were applied, as > detailed in the patch's commit message. I believe the current output > is still quite human readable. Overall this does not seem very worthwhile to me. One thing caught my eye though: We currently have an "open" command after every "create". Except for bootstrap relations; creating a bootstrap relation opens it implicitly. That seems like a weird inconsistency. If we make "create" to always open the relation, we can both make it more consistent and save a few lines. That's maybe worth doing, per the attached. It removes the "open" command altogether, as it's not needed anymore. Looking at "perf" profile of initdb, I also noticed that a small but measurable amount of time is spent in the "isatty(0)" call in do_end(). Does anyone care about doing bootstrap mode interactively? We could probably remove that. -- Heikki Linnakangas Neon (https://neon.tech)
Вложения
В списке pgsql-hackers по дате отправления: