pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Stephen Frost <sfrost@snowman.net>
Cc: Vladimir Borodin <root@simply.name>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>
Cc: Madusudanan.B.N <b.n.madusudanan@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Cc: David Steele <david@pgmasters.net>
Subject: Re: Backup taking long time !!!
Date: Mon, 23 Jan 2017 09:31:29 -0600
Message-ID: <1ddb6452-b5c0-9ee7-7f76-cdca5563a60b@BlueTreble.com> (raw )
In-Reply-To: <20170123152722.GX18360@tamriel.snowman.net >
References: <23dc5b1ea9604ec3afdaabdd15491085@cyient.com >
<CAFj8pRAHx-Wt4fyJmF=YH-F2_S=mO2E+=JDx+qnunkDP5_FPGA@mail.gmail.com >
<b0748fe40949446283068a4d2d06c158@cyient.com >
<CAFj8pRBFDh=hsghE8v5F71KztyczR7iWBXGJBOLLhUQDwUh8MQ@mail.gmail.com >
<20170120122224.GF18360@tamriel.snowman.net >
<DE553F58-646E-49E8-94D1-31794C3E9040@simply.name >
<20170120134054.GH18360@tamriel.snowman.net >
<7696A57C-C871-4A45-9141-FFD5F75CCB65@simply.name >
<20170120150646.GP18360@tamriel.snowman.net >
<68f87a97-15c2-5e4e-5730-77f9af2ca165@BlueTreble.com >
<20170123152722.GX18360@tamriel.snowman.net >
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 1/23/17 9:27 AM, Stephen Frost wrote:
> If you want my 2c on that, running with BLKSZ <> 8192 is playing with
> fire, or at least running with scissors.
I've never seen it myself, but I'm under the impression that it's not
unheard of for OLAP environments. Given how sensitive PG is to IO
latency a larger block size could theoretically mean a big performance
improvement in some scenarios.
--
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)
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
view thread (42+ messages) latest in thread
Message-ID: <1ddb6452-b5c0-9ee7-7f76-cdca5563a60b@BlueTreble.com>
Permalink: ../1ddb6452-b5c0-9ee7-7f76-cdca5563a60b@BlueTreble.com/
Also on: postgresql.org/message-id/1ddb6452-b5c0-9ee7-7f76-cdca5563a60b@BlueTreble.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: Jim.Nasby@BlueTreble.com, sfrost@snowman.net, root@simply.name, pavel.stehule@gmail.com, Dinesh.Chandra@cyient.com, b.n.madusudanan@gmail.com, david@pgmasters.net
Subject: Re: Backup taking long time !!!
In-Reply-To: <1ddb6452-b5c0-9ee7-7f76-cdca5563a60b@BlueTreble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox