Re: Preserve attstattarget on REINDEX CONCURRENTLY
Tomas Vondra <tomas.vondra@enterprisedb.com>
From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Ronan Dunklau <ronan@dunklau.fr>, pgsql-hackers@postgresql.org
Date: 2021-02-04T14:46:50Z
Lists: pgsql-hackers
On 2/4/21 11:04 AM, Ronan Dunklau wrote:
> Hello !
>
> ...
>
> junk=# REINDEX INDEX CONCURRENTLY t1_date_trunc_idx;
> REINDEX
> junk=# \d+ t1_date_trunc_idx
> Index "public.t1_date_trunc_idx"
> Column | Type | Key? | Definition
> | Storage | Stats target
> ------------+-----------------------------+------
> +-----------------------------+---------+--------------
> date_trunc | timestamp without time zone | yes | date_trunc('day'::text, ts)
> | plain |
> btree, for table "public.t1"
>
>
> I'm attaching a patch possibly solving the problem, but maybe the proposed
> changes will be too intrusive ?
>
Hmmm, that sure seems like a bug, or at least unexpected behavior (that
I don't see mentioned in the docs).
But the patch seems borked in some way:
$ patch -p1 < ~/keep_attstattargets_on_reindex_concurrently.patch
patch: **** Only garbage was found in the patch input.
There seem to be strange escape characters and so on, how did you create
the patch? Maybe some syntax coloring, or something?
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Commits
-
Fix ORDER BY clause in new regression test of REINDEX CONCURRENTLY
- 5b2945ec0a39 12.7 landed
- c6cd20d91ce9 13.3 landed
- 4f4726005082 14.0 landed
-
Preserve pg_attribute.attstattarget across REINDEX CONCURRENTLY
- 85edb1f2615d 12.7 landed
- 849383138581 13.3 landed
- bd1208098029 14.0 landed