| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Tobias Gierke <tobias(dot)gierke(at)code-sourcery(dot)de>, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Linear slow-down while inserting into a table with an ON INSERT trigger ? |
| Date: | 2021-07-19 05:45:02 |
| Message-ID: | a1aa5745d309e58dab73c1a1ee10cff1ae52b57c.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Sun, 2021-07-18 at 09:36 +0200, Tobias Gierke wrote:
> Thank you for the detailed explanation ! Just one more question: I've
> did an experiment and reduced the fillfactor on the table updated by the
> trigger to 50%, hoping the HOT feature would kick in and each
> subsequent INSERT would clean up the "HOT chain" of the previous INSERT
> ... but execution times did not change at all compared to 100%
> fillfactor, why is this ? Does the HOT feature only work if a different
> backend accesses the table concurrently ?
No, but until the transaction is done, the tuples cannot be removed,
no matter if they are HOT or not.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manish Lad | 2021-07-19 10:09:54 | Performance benchmark of PG |
| Previous Message | Tobias Gierke | 2021-07-18 07:36:33 | Re: Linear slow-down while inserting into a table with an ON INSERT trigger ? |