From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgsql: Compute XID horizon for page level index vacuum on primary. |
Date: | 2019-04-01 20:37:06 |
Message-ID: | CA+hUKG+0MtHfiWjcExzZaz9ShX=zroeeL8rpwrfbmL7DFUZGmQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Sat, Mar 30, 2019 at 11:32 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> Here's an attempt to write a suitable comment for the quick fix. And
> I suppose effective_io_concurrency is a reasonable default.
Pushed.
--
Thomas Munro
https://enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-04-01 21:37:42 | pgsql: Restrict pgbench's zipfian parameter to ensure good performance. |
Previous Message | Thomas Munro | 2019-04-01 20:31:53 | pgsql: Fix deadlock in heap_compute_xid_horizon_for_tuples(). |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2019-04-01 20:39:09 | Re: C_C_A animal on HEAD gets stuck in initdb |
Previous Message | legrand legrand | 2019-04-01 20:35:19 | Re: Planning counters in pg_stat_statements (using pgss_store) |