From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: REINDEX CONCURRENTLY unexpectedly fails |
Date: | 2019-11-13 14:36:37 |
Message-ID: | CAMkU=1zfiK9wV7KqtFBMMoyPnM9T_F=SvnUJPao1hC7AUZy6KQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Nov 13, 2019 at 9:30 AM Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>
wrote:
> Hi everyone,
>
> On the latest trunk version, I get an error "index "t0_pkey_ccnew"
> already contains data" when using REINDEX CONCURRENTLY:
>
> CREATE TEMP TABLE t0(c1 INT PRIMARY KEY) ON COMMIT DELETE ROWS;
> REINDEX TABLE CONCURRENTLY t0; -- unexpected: ERROR: index
> "t0_pkey_ccnew" already contains data
>
> Is this expected? I think I did not observe this error on earlier
> PostgreSQL versions.
>
For what it is worth, I get the samer error in 12.0. And the command
doesn't exist in 11.
The "ON COMMIT DELETE ROWS" is necessary to repodcue the problem, but the
index doesn't need to be primary key.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2019-11-13 14:50:04 | Re: BUG #16112: large, unexpected memory consumption |
Previous Message | Manuel Rigger | 2019-11-13 14:29:53 | REINDEX CONCURRENTLY unexpectedly fails |