Re: tuple concurrently updated

On 2018-Aug-28, wambacher(at)posteo(dot)de wrote:

> 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

> >              Spalte              |            Typ            |
> > Sortierfolge | NULL erlaubt? | Vorgabewert
> > ---------------------------------+---------------------------+--------------+---------------+-------------

> >  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«

I bet that something is happening to the special Postgis catalog table
for the geometry type when you run this update. Maybe, say, if you have
two such updates in a transaction, things break. The innards of
geometry_in are, um, fascinating (though I can't tell for sure whether
it tries to modify anything).

Also, I wouldn't put my hands to the fire for the gist support for it.

I further bet you'd have more luck asking a Postgis mailing list rather
than pgsql-admin.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services