| From: | Timur Birsh <taem(at)linukz(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | [PATCH] vacuumlo: print the number of large objects going to be removed |
| Date: | 2019-06-12 06:20:44 |
| Message-ID: | 18232791560320444@sas2-2074c606c35d.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
If tables has a lot of rows with large objects (>1_000_000) that
removed throughout the day, it would be useful to know how many
LOs going to be removed.
First patch - print the number of large objects going to be removed,
second patch - print how many LOs removed in percent.
Can anyone please review.
Please cc, I am not subscribed to the list.
Regards,
Timur
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-vacuumlo-print-the-number-of-large-objects-going-to-.patch | text/x-diff | 1.5 KB |
| 0002-vacuumlo-print-how-many-LOs-removed-in-percent.patch | text/x-diff | 791 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2019-06-12 06:23:33 | Re: pgbench rate limiting changes transaction latency computation |
| Previous Message | Etsuro Fujita | 2019-06-12 06:13:56 | Re: BEFORE UPDATE trigger on postgres_fdw table not work |