| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: REINDEX CONCURRENTLY unexpectedly fails |
| Date: | 2019-11-15 03:21:41 |
| Message-ID: | 20191115032141.GH1849@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tang, Haiying | 2019-11-15 04:23:01 | RE: BUG #16108: Colorization to the output of command-line has unproperly behaviors at Windows platform |
| Previous Message | Fan|| | 2019-11-15 03:12:18 | Re: Re： BUG #16102: Table can't be drop on PostgreSQL 10.09 if the table was createdfrom PostgreSQL 10.10 |