| From: | Arthur Cheysson <site(at)lafranceinsoumise(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Przemysław Szustak <przemyslaw(dot)szustak(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Subject: | Re: BUG #16283: crash on create index segmentation fault |
| Date: | 2020-05-21 17:01:06 |
| Message-ID: | ac5da643-cf63-a795-e114-ed3663b0fc7e@lafranceinsoumise.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
I filed a bug with PostGIS, and I think I found the origin of the
segfault in my case: this segfault seems to happen whenever there are a
few empty points (with [nan, nan] as coordinates) in my column, in a
non-deterministic manner.
https://trac.osgeo.org/postgis/attachment/ticket/4691/
Regards,
Arthur
Le 18/05/2020 à 18:22, Tom Lane a écrit :
> Arthur Cheysson <site(at)lafranceinsoumise(dot)fr> writes:
>> I am facing what seems to be the exact same problem, but with more
>> recent versions of both PostgreSQL and PostGIS
> Given that stack trace, you need to be reporting this to the PostGIS
> folk, not here.
>
> They'll likely ask you for a reproducible test case, too ...
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2020-05-21 23:45:42 | Re: Unique constraint error instead of serialization_failure |
| Previous Message | PG Bug reporting form | 2020-05-21 11:39:07 | BUG #16455: Broken RPMs python-ldap2pg postgresql11-devel |