| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | ktr(at)goldin-rudahl(dot)com |
| Subject: | BUG #15023: problem with pg_statistic |
| Date: | 2018-01-21 02:59:24 |
| Message-ID: | 20180121025924.3633.29967@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: 15023
Logged by: kurt rudahl
Email address: ktr(at)goldin-rudahl(dot)com
PostgreSQL version: Unsupported/Unknown
Operating system: linux
Description:
Problem: cannot reindex pg_statistic
therefore cannot vacuum
Steps to recreate:
1. restart postgresql
2. psql thaistocks
\set VERBOSITY verbose
thaistocks=# reindex table pg_statistic;
ERROR: 23505: could not create unique index
DETAIL: Table contains duplicated values.
LOCATION: comparetup_index, tuplesort.c:2163
thaistocks=# select starelid,staattnum from pg_statistic group by
starelid,staattnum having count(*) > 1;
starelid | staattnum
----------+-----------
10723 | 5
10728 | 1
1260 | 9
(3 rows)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2018-01-21 14:15:34 | BUG #15024: I am a beginer and in learning face |
| Previous Message | Tomas Vondra | 2018-01-21 01:08:25 | Re: BUG #15001: planner cann't distinguish composite index? |