It's not currently possible. The --truncate-apidb and --write-apidb tasks
have to be run via separate Osmosis invocations (to ensure one completes
before the other starts), and cannot be made to run inside a single
transaction.
Note that the import itself does run in a transaction, but doesn't
Thanks. Any hints on how this can be done with osmosis?
On 24.03.2010 21:12, Peter Körner wrote:
Import in a transaction.
___
osmosis-dev mailing list
osmosis-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/osmosis-dev
You're right, it's no fun at all.
Well here's what I did to try it with a smaller country excerpt (102
MB compressed) this night:
nohup bzcat ~/install/osm-dumps/austria.osm.bz2 |
./osmosis-0.34/bin/osmosis --read-xml-0.6 file=- --write-apidb-0.6
populateCurrentTables=yes host=localhost
Hi,
Klemens wrote:
So at some time in the future when I want
to import Europe into a DB that contains Austria I will have to create a
delta .osm first using osmosis?
Possible, but impractical, because you would spend more time to create
the delta than you save by re-using the existing data.
Am 24.03.2010 20:10, schrieb Klemens:
That makes sense. My requirement is that I must continue querying the
old data while importing the new, larger data - which can take a long
time as we know. How can I achieve this?
Import in a transaction.
Peter
Hi,
Klemens wrote:
That makes sense. My requirement is that I must continue querying the
old data while importing the new, larger data - which can take a long
time as we know. How can I achieve this?
I would suggest to create a second database instance (same server
process, different
I keep replying myself ;)
In the meantime I dropped the whole database and started with a clean
one. The import of austria.osm finished after about 100 minutes and
everything seems to be in the DB.
Probably the problems were due to an inconsistent state of the DB. I got
'Caused by:
That makes sense. My requirement is that I must continue querying the
old data while importing the new, larger data - which can take a long
time as we know. How can I achieve this?
On 24.03.2010 19:24, Frederik Ramm wrote:
Possible, but impractical, because you would spend more time to create
Hi,
I made an import of the planet.osm file using osmosis - the process ran for
about five days. Now it finished but effectively the postgresql database is
empty. In the statistics I can see that Tuples inserted for the nodes
table is 564,050,700 and the size is 117 GB. But there are no rows in
9 matches
Mail list logo
