| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | wambacher(at)posteo(dot)de |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: tuple concurrently updated |
| Date: | 2018-08-28 14:33:01 |
| Message-ID: | 20180828143301.g5gsjo7onyys2gyg@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 2018-Aug-28, wambacher(at)posteo(dot)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?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | wambacher | 2018-08-28 14:50:37 | Re: tuple concurrently updated |
| Previous Message | wambacher | 2018-08-28 14:21:20 | Re: tuple concurrently updated |