| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] [PATCH] Vacuum: Update FSM more frequently |
| Date: | 2018-02-08 15:45:15 |
| Message-ID: | CAGTBQpadngogX7CL2gohdrEAupTpqnmYwTUhOS7JNYFHROb3Tw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Feb 8, 2018 at 1:36 AM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> On Tue, Feb 6, 2018 at 9:51 PM, Claudio Freire <klaussfreire(at)gmail(dot)com> wrote:
>> I can look into doing 3, that *might* get rid of the need to do that
>> initial FSM vacuum, but all other intermediate vacuums are still
>> needed.
>
> Understood. So how about that this patch focuses only make FSM vacuum
> more frequently and leaves the initial FSM vacuum and the handling
> cancellation cases? The rest can be a separate patch.
Ok.
Attached split patches. All but the initial FSM pass is in 1, the
initial FSM pass as in the original patch is in 2.
I will post an alternative patch for 2 when/if I have one. In the
meanwhile, we can talk about 1.
| Attachment | Content-Type | Size |
|---|---|---|
| 0002-Vacuum-do-a-partial-FSM-vacuum-at-the-beginning.patch | text/x-patch | 2.2 KB |
| 0001-Vacuum-Update-FSM-more-frequently-v3.patch | text/x-patch | 12.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | amul sul | 2018-02-08 15:54:16 | Re: In logical replication concurrent update of partition key creates a duplicate record on standby. |
| Previous Message | Tom Lane | 2018-02-08 14:28:10 | Re: Disabling src/test/[ssl|ldap] when not building with SSL/LDAP support |