| From: | Wyatt Tellis <wyatt(dot)tellis(at)gmail(dot)com> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Improving pg_dump performance when handling large numbers of LOBs |
| Date: | 2024-02-05 19:55:43 |
| Message-ID: | CANCMp8wRi=v9vrf4HyvX9XHjyoxuu-gM8WRoUNnF+fBdmWGevw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Yes, the LOBs themselves are tiny, but there are a lot of them (~150
million) which seem to be slowing down pg_dump. Note, we did not
design/build this system and agree that use of LOBs for this purpose was
not necessary.
Wyatt
On Mon, Feb 5, 2024 at 11:36 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
> On Mon, Feb 5, 2024 at 2:01 PM Wyatt Tellis <wyatt(dot)tellis(at)gmail(dot)com>
> wrote:
>
>> Hi,
>>
>> We've inherited a series of legacy PG 12 clusters that each contain a
>> database that we need to migrate to a PG 15 cluster. Each database contains
>> about 150 million large objects totaling about 250GB.
>>
>
> 250*10^9 / (150*10^6) = 1667 bytes. That's *tiny*.
>
> Am I misunderstanding you?
>
>>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2024-02-05 20:05:29 | Re: Improving pg_dump performance when handling large numbers of LOBs |
| Previous Message | Adrian Klaver | 2024-02-05 19:53:27 | Re: Improving pg_dump performance when handling large numbers of LOBs |