| From: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, 李杰(慎追) <adger(dot)lj(at)alibaba-inc(dot)com>, 曾文旌(义从) <wenjing(dot)zwj(at)alibaba-inc(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Subject: | Re: CREATE INDEX CONCURRENTLY on partitioned index |
| Date: | 2022-06-29 08:01:37 |
| Message-ID: | bec008ae632d54b3d81af2ca86419732@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Justin Pryzby писал 2022-06-28 21:33:
> Hi,
>
> On Thu, Feb 10, 2022 at 06:07:08PM +0300, Alexander Pyhalov wrote:
>> I've rebased patches and tried to fix issues I've seen. I've fixed
>> reference
>> after table_close() in the first patch (can be seen while building
>> with
>> CPPFLAGS='-DRELCACHE_FORCE_RELEASE').
>
Rebased patches on the current master.
They still require proper review.
--
Best regards,
Alexander Pyhalov,
Postgres Professional
| Attachment | Content-Type | Size |
|---|---|---|
| v3-0005-Mark-intermediate-partitioned-indexes-as-valid.patch | text/x-diff | 8.3 KB |
| v3-0004-ReindexPartitions-to-set-indisvalid.patch | text/x-diff | 2.4 KB |
| v3-0003-Try-to-fix-create-index-progress-report.patch | text/x-diff | 7.7 KB |
| v3-0002-Add-SKIPVALID-flag-for-more-integration.patch | text/x-diff | 3.9 KB |
| v3-0001-Allow-CREATE-INDEX-CONCURRENTLY-on-partitioned-table.patch | text/x-diff | 15.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yugo NAGATA | 2022-06-29 08:29:50 | Re: Prevent writes on large objects in read-only transactions |
| Previous Message | Hannu Krosing | 2022-06-29 07:45:59 | Re: Hardening PostgreSQL via (optional) ban on local file system access |