| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Replication/backup defaults |
| Date: | 2017-01-08 01:19:11 |
| Message-ID: | 0a9c2968-3c2e-1c8b-a969-d51fc2a93cc3@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2017-01-08 01:26:28 | Re: Adding type info etc for inheritance errmsg: "child table is missing column ..." |
| Previous Message | Jim Nasby | 2017-01-08 01:09:22 | Re: pg_stat_activity.waiting_start |