| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | depesz(at)depesz(dot)com |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Can we get rid of repeated queries from pg_dump? |
| Date: | 2021-08-26 14:02:07 |
| Message-ID: | 648517.1629986527@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> It seems that for every function, pg_dump is getting it's data, and then
> runs format_type on each parameter/output type? I'm mostly guessing
> here, as I didn't read the code.
> Wouldn't it be possible to get all type formats at once, and cache them
> in pg_dump? Or at the very least reuse already received information?
Send a patch ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2021-08-26 14:08:27 | Re: Can we get rid of repeated queries from pg_dump? |
| Previous Message | Tom Lane | 2021-08-26 14:00:01 | Re: lower() and unaccent() not leakproof |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Denis Laxalde | 2021-08-26 14:07:40 | Re: [PATCH] Disable bgworkers during servers start in pg_upgrade |
| Previous Message | Daniel Gustafsson | 2021-08-26 13:59:49 | Re: [PATCH] Disable bgworkers during servers start in pg_upgrade |