Re: index fragmentation on insert-only table with non-unique column

From: Kevin Grittner <kgrittn(at)gmail(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: index fragmentation on insert-only table with non-unique column
Date: 2016-06-04 13:39:48
Message-ID: CACjxUsMS9zu=WT5TjoEwrb4v6rb-HNqSgA-WL7wsuxRbuR8Ttw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Jun 3, 2016 at 6:54 PM, Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:

> max_wal_size | 4GB | configuration file
> min_wal_size | 6GB | configuration file

Just a minor digression -- it generally doesn't make sense to
configure the minimum for something greater than the maximum for
that same thing. That should have no bearing the performance issue
raised on the thread, but you might want to fix it anyway.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2016-06-05 16:03:58 Re: index fragmentation on insert-only table with non-unique column
Previous Message Venkata Balaji N 2016-06-04 08:10:18 Re: pg_database_size