Re: BUG #18016: REINDEX TABLE failure

From: Gurjeet Singh <gurjeet(at)singh(dot)im>
To: Richard Veselý <richard(dot)vesely(at)softea(dot)sk>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: BUG #18016: REINDEX TABLE failure
Date: 2023-07-10 16:43:49
Message-ID: CABwTF4UZB-cUSwfB7hQC2uosA2j0XBnL8JShB8oDuL-KBEdgJA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On Sun, Jul 9, 2023 at 7:21 AM Richard Veselý <richard(dot)vesely(at)softea(dot)sk> wrote:
>
> ... there's no shortage of people that suffer from sluggish pg_dump/pg_restore cycle and I imagine there are any number of people that would be interested in improving bulk ingestion which is often a bottleneck for analytical workloads as you are well aware. What's the best place to discuss this topic further - pgsql-performance or someplace else?

(moved conversation to -hackers, and moved -bugs to BCC)

> I was dissatisfied with storage layer performance, especially during the initial database population, so I rewrote it for my use case. I'm done with the heap, but for the moment I still rely on PostgreSQL to build indexes,

It sounds like you've developed a method to speed up loading of
tables, and might have ideas/suggestions for speeding up CREATE
INDEX/REINDEX. The -hackers list feels like a place to discuss such
changes.

Best regards,
Gurjeet
http://Gurje.et

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2023-07-10 19:51:07 Re: BUG #17994: Invalidating relcache corrupts tupDesc inside ExecEvalFieldStoreDeForm()
Previous Message Gurjeet Singh 2023-07-10 16:35:05 Re: BUG #18016: REINDEX TABLE failure

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2023-07-10 16:50:38 Re: UUID v7
Previous Message Gurjeet Singh 2023-07-10 16:35:05 Re: BUG #18016: REINDEX TABLE failure