| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | mcinp(at)o2(dot)pl |
| Subject: | BUG #15066: Index size on column of nulls |
| Date: | 2018-02-14 14:10:39 |
| Message-ID: | 151861743953.1459.8434970197838678416@wrigleys.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 15066
Logged by: Marcin Piotrowski
Email address: mcinp(at)o2(dot)pl
PostgreSQL version: 9.6.7
Operating system: Ubuntu 16.04
Description:
TL;DR
Gist index goes really huge when updating records, even if gist indexed
column is not changed.
Full story:
I already created a ticket for this, but was redirected to PostGIS.
Now it seems it's not PostGIS, but PG itself, as shown in
https://trac.osgeo.org/postgis/ticket/3716
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-02-14 14:44:50 | BUG #15067: Documentation or behaviour bug with autovacuum thresholds? |
| Previous Message | Heath Lord | 2018-02-14 13:27:09 | Re: BUG #15065: ActivePerl 5.24.3 breaks PG compilation on Windows |