From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
---|---|
To: | Darafei Komяpa Praliaskouski <me(at)komzpa(dot)net> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] COPY FREEZE and PD_ALL_VISIBLE |
Date: | 2019-02-21 06:07:56 |
Message-ID: | CABOikdNJLVQF-AAOQ44FogvzhJojK+H-OoaSfwdD2mLmGB0zvw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 15, 2019 at 8:48 PM Darafei "Komяpa" Praliaskouski <
me(at)komzpa(dot)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:
>
> https://gist.github.com/Komzpa/e765c1c5e04623d83a6263d4833cf3a5
>
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tsunakawa, Takayuki | 2019-02-21 06:11:51 | RE: Protect syscache from bloating with negative cache entries |
Previous Message | Pavan Deolasee | 2019-02-21 06:05:14 | COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits |