Re: index fragmentation on insert-only table with non-unique column - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: index fragmentation on insert-only table with non-unique column
Date
Msg-id CACjxUsMS9zu=WT5TjoEwrb4v6rb-HNqSgA-WL7wsuxRbuR8Ttw@mail.gmail.com
Whole thread Raw
In response to Re: index fragmentation on insert-only table with non-unique column  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-performance
On Fri, Jun 3, 2016 at 6:54 PM, Justin Pryzby <pryzby@telsasoft.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


pgsql-performance by date:

Previous
From: Venkata Balaji N
Date:
Subject: Re: pg_database_size
Next
From: Tom Lane
Date:
Subject: Re: index fragmentation on insert-only table with non-unique column