| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Janning Vygen <vygen(at)kicktipp(dot)de> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: slow pg_dump with bytea |
| Date: | 2023-10-20 13:18:19 |
| Message-ID: | 202310201318.ukcklynpe5bq@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2023-Oct-20, Janning Vygen wrote:
> So maybe you can fix it by changing the pg_dump process to not compress any
> bytea data.
The problem with this idea is that the compression applies to the whole
data stream. The backup format doesn't allow to compress some columns
and not others. Doing that would require a lot of changes to pg_dump.
Maybe a workable idea would be to allow excluding individual tables from
being compressed.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-10-20 19:03:25 | Re: group by true now errors with non-integer constant in GROUP BY |
| Previous Message | Laurenz Albe | 2023-10-20 12:51:30 | Re: slow pg_dump with bytea |