Thanks Maxim and Jeff.
1. Do you have any pointers to the killbits issue on hot standby slaves? We
do use a hot standby instance for many queries. So I want to learn more
about it.
2. I am now considering partitioning the table. I am curious if we can set
up partitions by mutable columns. More spec
Thanks Maxim, that's something we are considering now - keep the in
progress tasks in one table and periodically move the old and completed
tasks to an archive table.
We could use a view that unions them for most queries.
I'm not sure if that's the best alternative though, and we want to know if
t
On Tue, Aug 29, 2023, 12:43 PM Jeff Janes wrote:
> On Mon, Aug 28, 2023 at 8:33 PM jayaprabhakar k
> wrote:
>
>> Hi,
>>
>> TL;DR:
>> Observations:
>>
>>1. REINDEX requires a full table scan
>> - Roughly create a new index, rena
86_64-pc-linux-gnu-gcc (GCC) 7.4.0, 64-bit
(1 row)
On Mon, 28 Aug 2023 at 18:49, Peter Geoghegan wrote:
> On Mon, Aug 28, 2023 at 5:33 PM jayaprabhakar k
> wrote:
> > REINDEX requires a full table scan
> >
> > Roughly create a new index, rename index, drop old ind
Hi,
TL;DR:
Observations:
1. REINDEX requires a full table scan
- Roughly create a new index, rename index, drop old index.
- REINDEX is not incremental. running reindex frequently does not
reduce the future reindex time.
2. REINDEX does not use the index itself
3. VACUU
