Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from
 <pgsql-performance-owner+M54660=pgsql-performance-ar@postgresql.org>)
	id 1cGtUu-0003cJ-0A
	for pgsql-performance@arkaria.postgresql.org; Tue, 13 Dec 2016 20:16:24 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.84_2)
	(envelope-from
 <pgsql-performance-owner+M54660=pgsql-performance-ar@postgresql.org>)
	id 1cGtUs-00050V-Cd
	for pgsql-performance@arkaria.postgresql.org; Tue, 13 Dec 2016 20:16:22 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <dba@propaas.com>)
	id 1cGtUr-0004zr-0f
	for pgsql-performance@postgresql.org; Tue, 13 Dec 2016 20:16:21 +0000
Received: from mail-io0-x243.google.com ([2607:f8b0:4001:c06::243])
	by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.84_2)
	(envelope-from <dba@propaas.com>)
	id 1cGtUn-0000ss-PJ
	for pgsql-performance@postgresql.org; Tue, 13 Dec 2016 20:16:19 +0000
Received: by mail-io0-x243.google.com with SMTP id p13so400473ioi.0
        for <pgsql-performance@postgresql.org>;
 Tue, 13 Dec 2016 12:16:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=propaas-com.20150623.gappssmtp.com; s=20150623;
        h=to:from:subject:message-id:date:user-agent:mime-version
         :content-transfer-encoding;
        bh=sPgYNOKW7j3+vcGy1iNKVD1wxOhkRGmGZB6Y0TWtAdk=;
        b=JwkvRJUrXclvAcsxFw8A3qe4Bpw5KzbiK3uMa8BL3HTc30uFxcmXVJ0YA1zyIBMyUW
         kMXfoUFDI3v5JTeCsbVGc+Nx/6abqLuI5Ko9U9DnuqUdvsR8HE278Ig8Tzq6L+ppsXRy
         mjgDWaq1AxuuQZ+i1g+d1z7VxiB+6BbdErzkotANZ7rFG7wqHfpPCj6xN832dYephmJo
         Bxwz9/lWnTwVY+fks24MqBqIdGtDgF182SQe4MGr8wMQxHy+Eg2D0Q+KHucuUw0H2KLT
         kcnNbP/uXaEMfLTYbUeXSsSGkvYDWr4ZZaChZmcAaGgwGW9HgRTDcX1j0M5y7slL5T3O
         SK9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:to:from:subject:message-id:date:user-agent
         :mime-version:content-transfer-encoding;
        bh=sPgYNOKW7j3+vcGy1iNKVD1wxOhkRGmGZB6Y0TWtAdk=;
        b=kI3IX5OIRb+f3ImTPD+/g6nKhGENukftd/Fzc4B9G4KJq0qZ7PW3eK/l9trxDhG1vb
         DC6OSf5J4b4oizPwzdWyHKWi5XtK1Xt6UWjhwy2v2UvuwDLwfJLFXrOOEieD4v7lRwJM
         Rapzl6zxZKqfKApB/Msuv0nRQF53r+eD47GU+gWz9UyjfclmThUpd5pKDjn9XK4PX6q6
         5eydfHdzA4sLz1FZHQ0P8yvemsXKuF70SyhVG3BP7dLbqDBepydKJ5GwJj5Vgin8AKYW
         ZOMnbUwVdTkmrp2vQrFtIYfxKVK/K47CdEzllBe/9Y55pelfVT3Y8y+0IYsKLK2aQXkE
         eBEg==
X-Gm-Message-State: 
 AKaTC03rKVsS3cnrJjGcV7ChVumdgtraghuSqMSDUZFA+rFzJn2lFCw9gngflnsURW9Smw==
X-Received: by 10.36.211.137 with SMTP id n131mr4162658itg.28.1481660176356;
        Tue, 13 Dec 2016 12:16:16 -0800 (PST)
Received: from [192.168.1.17] (c-24-9-41-137.hsd1.co.comcast.net.
 [24.9.41.137])
        by smtp.gmail.com with ESMTPSA id
 b81sm21814614iob.31.2016.12.13.12.16.15
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Tue, 13 Dec 2016 12:16:15 -0800 (PST)
To: pgsql-performance@postgresql.org
From: ProPAAS DBA <dba@propaas.com>
Subject: Isolation of tx logs on VMware
Message-ID: <9998f9f1-bb96-2712-e823-a5f712505668@propaas.com>
Date: Tue, 13 Dec 2016 13:16:14 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.5.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -1.9 (-)
List-Archive: <http://archives.postgresql.org/pgsql-performance>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-performance.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@postgresql.org>
List-Post: <mailto:pgsql-performance@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-performance>
List-Unsubscribe: 
 <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
X-Mailing-List: pgsql-performance
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Hi All;


We have a client running on VMware, they have heavy write traffic and we 
want to isolate the IO for the tx logs (pg_xlog). However it seems the 
best plan based on feedback from the client is either

(a) simply leave the pg_xlog dir in the VMDK

or

(b) relocate pg_xlog to NAS/NFS


I'm not a VMware expert, however I thought VMware would allow the 
creation of multiple disk volumes and attach them via separate mount 
points. Is this not true? If it is an option can someone point me to a 
how to...


Also, if we cannot do multiple VMDK volumes then what is everyone's 
thoughts about relocating pg_xlog to an NFS mount?


Thanks in advance





-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance