pg.ddx.io pgsql-bugs@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Heikki Linnakangas <hlinnaka@iki.fi>
Cc: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Manuel Rigger <rigger.manuel@gmail.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: REINDEX CONCURRENTLY unexpectedly fails
Date: Tue, 14 Jan 2020 17:47:09 +0900
Message-ID: <20200114084709.GI1515@paquier.xyz> (raw)
In-Reply-To: <20200109030619.GC2251@paquier.xyz>
References: <20191115032141.GH1849@paquier.xyz>
<20191115080706.GI1849@paquier.xyz>
<20191120013649.2xfr2dnznyjgluch@alap3.anarazel.de>
<20191120035408.GA4243@paquier.xyz>
<20191212213709.neopqccvdo724eha@alap3.anarazel.de>
<20191213034536.GD1942@paquier.xyz>
<20191223015956.GB34339@paquier.xyz>
<8f0bde7b-2d96-fb5c-cd0e-553694c1d376@iki.fi>
<20200108081930.GF3413@paquier.xyz>
<20200109030619.GC2251@paquier.xyz>
Hi Heikki,
On Thu, Jan 09, 2020 at 12:06:19PM +0900, Michael Paquier wrote:
> As the patch has been heavily modified, I am switching it back to
> "Needs Review" for now and I'd like to discuss more about the lock
> upgrade risks, particularly if it is considered worth the effort for
> temporary relations. Thoughts are welcome.
You are registered as a reviewer for this patch:
https://commitfest.postgresql.org/26/2358/
Are you planning to look at it? Do you have some thoughts to share
about what I wrote previously?
Discarding the lock upgrade considerations is possible. Another
approach would be, instead of ignoring CONCURRENTLY for temporary
tables, to fail if the operation is run, and ignore these when a
dabatase-wide reindex concurrently happens. This was not liked much
at the beginning of the thread though.
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
view thread (32+ messages) latest in thread
Message-ID: <20200114084709.GI1515@paquier.xyz> Permalink: ../20200114084709.GI1515@paquier.xyz/ Also on: postgresql.org/message-id/20200114084709.GI1515@paquier.xyz ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-bugs@postgresql.org Cc: michael@paquier.xyz, hlinnaka@iki.fi, andres@anarazel.de, tgl@sss.pgh.pa.us, rigger.manuel@gmail.com Subject: Re: REINDEX CONCURRENTLY unexpectedly fails In-Reply-To: <20200114084709.GI1515@paquier.xyz> References: <20191115032141.GH1849@paquier.xyz> <20191115080706.GI1849@paquier.xyz> <20191120013649.2xfr2dnznyjgluch@alap3.anarazel.de> <20191120035408.GA4243@paquier.xyz> <20191212213709.neopqccvdo724eha@alap3.anarazel.de> <20191213034536.GD1942@paquier.xyz> <20191223015956.GB34339@paquier.xyz> <8f0bde7b-2d96-fb5c-cd0e-553694c1d376@iki.fi> <20200108081930.GF3413@paquier.xyz> <20200109030619.GC2251@paquier.xyz> <20200114084709.GI1515@paquier.xyz> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox