From: | Ilya Gladyshev <ilya(dot)v(dot)gladyshev(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
Subject: | Re: CREATE INDEX CONCURRENTLY on partitioned index |
Date: | 2024-07-12 22:17:25 |
Message-ID: | 428008d6-911d-4a14-986f-0fbb74db6fd8@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
Attachment | Content-Type | Size |
---|---|---|
v5-0001-Allow-CREATE-INDEX-CONCURRENTLY-on-partitioned-ta.patch | text/x-patch | 28.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Melih Mutlu | 2024-07-12 22:32:55 | Re: Parent/child context relation in pg_get_backend_memory_contexts() |
Previous Message | Melih Mutlu | 2024-07-12 22:11:52 | Re: Parent/child context relation in pg_get_backend_memory_contexts() |