Re: [HACKERS] Replication/backup defaults - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [HACKERS] Replication/backup defaults
Date
Msg-id 0a9c2968-3c2e-1c8b-a969-d51fc2a93cc3@BlueTreble.com
Whole thread Raw
In response to Re: [HACKERS] Replication/backup defaults  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: [HACKERS] Replication/backup defaults  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On 1/5/17 2:50 PM, Tomas Vondra wrote:
> Ultimately, the question is whether the number of people running into
> "Hey, I can't take pg_basebackup or setup a standby with the default
> config!" is higher or lower than number of people running into "Hey,
> CREATE TABLE + COPY is slower now!"

I'm betting it's way higher. Loads of folks use Postgres and never do 
any kind of ETL.

> That is not to say there are no other cases benefiting from those
> optimizations, but we're talking about the default value - we're not
> removing the wal_level=minimal.

This would be a non-issue if we provided example configs for a few 
different workloads. Obviously those would never be optimal either, but 
they *would* show users what settings they should immediately look at 
changing in their environment.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] pg_stat_activity.waiting_start
Next
From: Jim Nasby
Date:
Subject: Re: [HACKERS] Adding type info etc for inheritance errmsg: "childtable is missing column ..."