Re: ADD COLUMN ts tsvector GENERATED too slow

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: Florents Tselai <florents(dot)tselai(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: ADD COLUMN ts tsvector GENERATED too slow
Date: 2022-07-06 14:32:08
Message-ID: CA+bJJbzMfvfAR+0UTQ0vzdTS3GuF1=R4+Z3w48-FLYteoybWig@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi Florents:

On Wed, 6 Jul 2022 at 12:35, Florents Tselai <florents(dot)tselai(at)gmail(dot)com> wrote:
> 50M+ rows and iirc pg_relation_size was north of 80GB or so.

Somebody already mentioned pg_table_size, but anyway this gives you
1.6Kb per row, which I would suspect is extremely low given your pdf
content and the 1M truncation you preventively applied.

When working with this kind of sizes it really pays to do some good
ole "back of the envelope" calculations and/or some tests with small
batches. Bear in mind if you have, say, 10k per row ( which I would
label as really low for pdf content ) you are going to have 500Gb of
data, if you manage to process this at 100Mb per second you will have
more than an hour ( and I think I'm estimating really low ).

FOS

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Matthias Apitz 2022-07-06 14:32:35 Re: lifetime of the old CTID
Previous Message Peter J. Holzer 2022-07-06 13:53:54 Re: lifetime of the old CTID