public inbox for [email protected]  

help / color / mirror / Atom feed

From: Justin Clift <[email protected]>
To: Alexander Farber <[email protected]>
Cc: [email protected]
Subject: Re: Please recommend postgresql.conf improvements for osm2pgsql loading Europe
Date: Sun, 31 Mar 2024 17:31:28 +1000
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAADeyWiX-8f2e+x=zmuiUrWWSbTd8HEp7ZKhzWLu_tr96+QOHw@mail.gmail.com>
References: <CAADeyWibmmfvBhJS2P2mPUOLx57WJ0h+qM5xBQPqFehh-Sna4g@mail.gmail.com>
	<[email protected]>
	<CAADeyWgKVA4BdJu7L+9Z7rXW06vMRhiLfQP1MixwCshOGpmZ7Q@mail.gmail.com>
	<CAADeyWiX-8f2e+x=zmuiUrWWSbTd8HEp7ZKhzWLu_tr96+QOHw@mail.gmail.com>

On 2024-03-31 04:07, Alexander Farber wrote:
> Turning fsync = off has resulted in no noticable build time reduction 
> for
> my Dockerfile with OSM Europe data, but still thank you for the 
> suggestion!

No worries. :)

With this import you're doing, is it something that will be repeated a 
lot
with the exact same data set, or is this a once off thing?

If it's something that'll be repeated a lot (maybe part of some 
automated
process?), then it might be worth making a backup / snapshot / something
of the database after the import has completed.

With a backup or snapshot in place (depends on the storage you're 
using),
you could potentially load things from that backup / snapshot (etc) 
instead
of having to do the import all over again each time.

Regards and best wishes,

Justin Clift

view thread (6+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Please recommend postgresql.conf improvements for osm2pgsql loading Europe
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox