| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Optimization for lazy_scan_heap |
| Date: | 2016-08-04 04:57:48 |
| Message-ID: | CAD21AoD1MEqz9-biWkfvErQ_S7meGqHSUoA6CfuDF93ik4SZrQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all,
While reviewing freeze map code, Andres pointed out[1] that
lazy_scan_heap could accesses visibility map twice and its logic is
seems a bit tricky.
As discussed before, it's not nice especially when large relation is
entirely frozen.
I posted the patch for that before but since this is an optimization,
not bug fix, I'd like to propose it again.
Please give me feedback.
[1] https://www.postgresql.org/message-id/20160505000840.epatoq6d2e556446%40alap3.anarazel.de
Regards,
--
Masahiko Sawada
| Attachment | Content-Type | Size |
|---|---|---|
| optimize_lazy_scan_heap_v1.patch | text/x-patch | 6.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-08-04 05:26:32 | Re: Tracking wait event for latches |
| Previous Message | Tom Lane | 2016-08-04 04:56:48 | Re: max_parallel_degree > 0 for 9.6 beta |