Re: Allowing REINDEX to have an optional name - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Allowing REINDEX to have an optional name
Date
Msg-id CANbhV-GDU9m5C48Xxhkng3oGriZUPhZ1me_y6-CJjBGSvUAvMw@mail.gmail.com
Whole thread Raw
In response to Re: Allowing REINDEX to have an optional name  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Allowing REINDEX to have an optional name
List pgsql-hackers
On Fri, 15 Jul 2022 at 04:44, Michael Paquier <michael@paquier.xyz> wrote:
>
> On Mon, Jul 04, 2022 at 03:59:55PM +0900, Michael Paquier wrote:
> > Please note that patch authors should not switch a patch as RfC by
> > themselves.  This is something that a reviewer should do.
>
> http://commitfest.cputube.org/simon-riggs.html

Thanks for showing me that, it is very helpful.

> This patch has been marked as waiting for a review, however the CF bot
> is completely red:

Yes, it is failing, but so is current HEAD, with some kind of libpq
pipelining error.

-- 
Simon Riggs                http://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Backup command and functions can cause assertion failure and segmentation fault
Next
From: Fujii Masao
Date:
Subject: Re: Add a test for "cannot truncate foreign table"