From: wambacher@posteo.de
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
Date: Tue, 28 Aug 2018 16:50:37 +0200
Message-ID: <fc354354-bf6a-622c-e045-d554c58d9b31@posteo.de> (raw)
In-Reply-To: <20180828143301.g5gsjo7onyys2gyg@alvherre.pgsql>
References: <20180828143301.g5gsjo7onyys2gyg@alvherre.pgsql>
no, i respect your questions, but i can't answer them. because i don't
know in detail what osm2pgsql is doing.
planet_osm_line it postgis
see:
> Tabelle »public.planet_osm_line«
> Spalte | Typ |
> Sortierfolge | NULL erlaubt? | Vorgabewert
> ---------------------------------+---------------------------+--------------+---------------+-------------
> osm_id | bigint
> | | |
> access | text
> | | |
> addr:housename | text
> | | |
> addr:housenumber | text
> | | |
> addr:interpolation | text
> | | |
> admin_level | text
> | | |
> aerialway | text
> | | |
> aeroway | text
> | | |
> amenity | text
> | | |
> area | text
> | | |
> barrier | text
> | | |
> bicycle | text
> | | |
> brand | text
> | | |
> bridge | text
> | | |
> boundary | text
> | | |
> building | text
> | | |
> construction | text
> | | |
> covered | text
> | | |
> culvert | text
> | | |
> cutting | text
> | | |
> denomination | text
> | | |
> disused | text
> | | |
> embankment | text
> | | |
> foot | text
> | | |
> generator:source | text
> | | |
> harbour | text
> | | |
> highway | text
> | | |
> historic | text
> | | |
> horse | text
> | | |
> intermittent | text
> | | |
> junction | text
> | | |
> landuse | text
> | | |
> layer | text
> | | |
> leisure | text
> | | |
> lock | text
> | | |
> man_made | text
> | | |
> military | text
> | | |
> motorcar | text
> | | |
> name | text
> | | |
> natural | text
> | | |
> office | text
> | | |
> oneway | text
> | | |
> operator | text
> | | |
> place | text
> | | |
> population | text
> | | |
> power | text
> | | |
> power_source | text
> | | |
> public_transport | text
> | | |
> railway | text
> | | |
> ref | text
> | | |
> religion | text
> | | |
> route | text
> | | |
> service | text
> | | |
> shop | text
> | | |
> sport | text
> | | |
> surface | text
> | | |
> toll | text
> | | |
> tourism | text
> | | |
> tower:type | text
> | | |
> tracktype | text
> | | |
> tunnel | text
> | | |
> water | text
> | | |
> waterway | text
> | | |
> wetland | text
> | | |
> width | text
> | | |
> wood | text
> | | |
> z_order | integer
> | | |
> way_area | real
> | | |
> addr:postcode | text
> | | |
> de:amtlicher_gemeindeschluessel | text
> | | |
> de:regionalschluessel | text
> | | |
> ISO3166-1:alpha3 | text
> | | |
> maxspeed | text
> | | |
> maxspeed:forward | text
> | | |
> maxspeed:backward | text
> | | |
> name:de | text
> | | |
> note | text
> | | |
> postal_code | text
> | | |
> tags | hstore
> | | |
> way | geometry(LineString,4326)
> | | |
> Indexe:
> "idx_planet_osm_line_highway" btree (highway)
> "planet_osm_line_index" gist (way), Tablespace »planet3_is1«
> "planet_osm_line_pkey" btree (osm_id), Tablespace »planet3_is1«
> "planet_osm_line_tags_index" gin (tags), Tablespace »planet3_is1«
> Tablespace: »planet3_ts1«
Am 28.08.2018 um 16:33 schrieb Alvaro Herrera:
> On 2018-Aug-28, wambacher@posteo.de wrote:
>
>> updates are done using a program, that is without my control: osm2pgsql.
>>
>> this program does everthing which is necessary including locking. and
>> it't running for years on many, many openstreetmap servers.
>>
>> because there was a crash before, it must be a data corruption problem,
>> not programming error.
> It's curious that you reply to my email and not respond to a single of
> the questions I posed, and instead answered questions I didn't ask.
> Perhaps you thought I asked them because I was bored?
>
>>> What is the definition of the table? It sounds like there's some GIS
>>> datatype -- Right? Are there any triggers or some other fun fact about
>>> this delete? What is the isolation level in effect when the delete
>>> runs?
--
My projects:
Admin Boundaries of the World <https://wambachers-osm.website/boundaries;
Missing Boundaries
<https://wambachers-osm.website/index.php/projekte/internationale-administrative-grenzen/missing-boun...;
Emergency Map <https://wambachers-osm.website/emergency;
Postal Code Map (Germany only) <https://wambachers-osm.website/plz;
Fools (QA for zipcodes in Germany) <https://wambachers-osm.website/fools;
Postcode Boundaries of Germany <https://wambachers-osm.website/pcoundaries;
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: pgsql-admin@postgresql.org
Cc: wambacher@posteo.de, alvherre@2ndquadrant.com, pgsql-admin@lists.postgresql.org
Subject: Re: tuple concurrently updated
In-Reply-To: <fc354354-bf6a-622c-e045-d554c58d9b31@posteo.de>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox