Re: REINDEX CONCURRENTLY unexpectedly fails - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: REINDEX CONCURRENTLY unexpectedly fails
Date
Msg-id 20191115032141.GH1849@paquier.xyz
Whole thread Raw
In response to Re: REINDEX CONCURRENTLY unexpectedly fails  (Andres Freund <andres@anarazel.de>)
Responses Re: REINDEX CONCURRENTLY unexpectedly fails  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
On Thu, Nov 14, 2019 at 06:54:12PM -0800, Andres Freund wrote:
> I think it'd be really user hostile if ReindexMultipleTables() suddenly
> started to error out if there were any temp tables. That clearly can't
> be an option.

Okay.

> Did you actually read the sub-thread before replying? That's literally
> what we are discussing:

Oh, sorry.  I got confused with the thread as I was not quite clear if
you were referring to work on temp tables only for the ones with
on-commit actions or all of them.  It makes sense to do so for all, as
you said.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: "Fan||"
Date:
Subject: Re: Re: BUG #16102: Table can't be drop on PostgreSQL 10.09 if the table was createdfrom PostgreSQL 10.10
Next
From: "Tang, Haiying"
Date:
Subject: RE: BUG #16108: Colorization to the output of command-line has unproperly behaviors at Windows platform