Re: [HACKERS] COPY FREEZE and PD_ALL_VISIBLE

Поиск
Список
Период
Сортировка
От Pavan Deolasee
Тема Re: [HACKERS] COPY FREEZE and PD_ALL_VISIBLE
Дата
Msg-id CABOikdNJLVQF-AAOQ44FogvzhJojK+H-OoaSfwdD2mLmGB0zvw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] COPY FREEZE and PD_ALL_VISIBLE  (Darafei "Komяpa" Praliaskouski <me@komzpa.net>)
Список pgsql-hackers
Дерево обсуждения

On Tue, Jan 15, 2019 at 8:48 PM Darafei "Komяpa" Praliaskouski <me@komzpa.net> wrote:
Hello,

Today I bumped into need to limit first VACUUM time on data import.
I'm using utility called osmium together with COPY FREEZE to import openstreetmap data into database.

osmium export -c osmium.config -f pg belarus-latest.osm.pbf  -v --progress | psql -1 -c 'create table byosm(geom geometry, osm_type text, osm_id bigint, tags jsonb);copy byosm from stdin freeze;'

However, first pass of VACUUM rewrites the whole table. Here is two logs of VACUUM VERBOSE in a row:


In Russian Postgres Telegram group I've been recommended this thread. 
Can the patch be revived? What is needed to get it up for 12?

I posted a new patch [1] for consideration to include in PG12. I started a new thread because the patch is completely new and this thread was a bit too old.

Thanks,
Pavan


--
 Pavan Deolasee                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Pavan Deolasee
Дата:
Сообщение: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits
Следующее
От: "Tsunakawa, Takayuki"
Дата:
Сообщение: RE: Protect syscache from bloating with negative cache entries