From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
---|---|
To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: WIP: parallel GiST index builds |
Date: | 2024-07-22 11:53:31 |
Message-ID: | e35e8f43-89a0-4267-8ab2-ef31eaf986ef@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 7/22/24 13:08, Andrey M. Borodin wrote:
>
>
>> On 22 Jul 2024, at 12:26, Tomas Vondra
>> <tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
>>
>> I don't understand how would that solve the problem, can you
>> elaborate? Which of the values are you suggesting should be
>> replaced with the shared counter? lastlsn?
>
> I think during build we should consider index unlogged and always use
> GetFakeLSNForUnloggedRel() or something similar. Anyway we will
> calllog_newpage_range(RelationGetNumberOfBlocks(index)) at the end.
>
But that doesn't update the page LSN, which GiST uses to detect
concurrent splits, no?
regards
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Bapat | 2024-07-22 12:01:42 | Re: SQL Property Graph Queries (SQL/PGQ) |
Previous Message | Amul Sul | 2024-07-22 11:52:07 | Re: pg_verifybackup: TAR format backup verification |