| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, "Imai, Yoshikazu" <imai(dot)yoshikazu(at)jp(dot)fujitsu(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Speed up transaction completion faster after many relations are accessed in a transaction |
| Date: | 2019-04-07 15:20:43 |
| Message-ID: | 27413.1554650443@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
> On Mon, 8 Apr 2019 at 02:59, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> We *should* be using hash_get_num_entries(), but only to verify
>> that the table is empty before resetting it. The additional bit
>> that is needed is to see whether the number of buckets is large
>> enough to justify calling the table bloated.
> The reason I thought it was a good idea to track some history there
> was to stop the lock table constantly being shrunk back to the default
> size every time a simple single table query was executed.
I think that's probably gilding the lily, considering that this whole
issue is pretty new. There's no evidence that expanding the local
lock table is a significant drag on queries that need a lot of locks.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2019-04-07 15:27:08 | Re: ToDo: show size of partitioned table |
| Previous Message | David Rowley | 2019-04-07 15:07:37 | Re: Speed up transaction completion faster after many relations are accessed in a transaction |