Horton
Menu

Re: CREATE INDEX CONCURRENTLY on partitioned index

Ilya Gladyshev <ilya.v.gladyshev@gmail.com>

View thread
From: Ilya Gladyshev <ilya.v.gladyshev@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Justin Pryzby <pryzby@telsasoft.com>, Alexander Pyhalov <a.pyhalov@postgrespro.ru>, pgsql-hackers@lists.postgresql.org, Masahiko Sawada <sawada.mshk@gmail.com>
Date: 2024-07-12T22:17:25Z
Lists: pgsql-hackers

Attachments

On 12.07.2024 01:01, Michael Paquier wrote:
> Please let's move this point to its own thread and deal with it with
> an independent patch.  Hiding that in a thread that's already quite
> long is not a good idea.  This needs proper review, and a separate
> thread with a good subject to describe the problem will attract a
> better audience to deal with the problem you are seeing.
>
> I was not paying much attention, until you've mentioned that this was
> an issue with HEAD.
> --
> Michael

Sure, created a separate thread [1]. Please disregard the second patch 
in this thread. Duplicating the last version of the relevant patch here 
to avoid any confusion.

[1] 
https://www.postgresql.org/message-id/b72f2d89-820a-4fa2-9058-b155cf646f4f%40gmail.com

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix assertion failure with REINDEX and event triggers