Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1j54zN-0001hh-T6
	for pgsql-admin@arkaria.postgresql.org; Fri, 21 Feb 2020 09:52:54 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1j54zL-0001ME-R1
	for pgsql-admin@arkaria.postgresql.org; Fri, 21 Feb 2020 09:52:51 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <jwo@disroot.org>)
	id 1j54zL-0001K6-FR
	for pgsql-admin@lists.postgresql.org; Fri, 21 Feb 2020 09:52:51 +0000
Received: from knopi.disroot.org ([178.21.23.139])
	by magus.postgresql.org with esmtps (TLS1.2:DHE_RSA_CHACHA20_POLY1305:256)
	(Exim 4.92)
	(envelope-from <jwo@disroot.org>)
	id 1j54zE-0006iM-GZ
	for pgsql-admin@lists.postgresql.org; Fri, 21 Feb 2020 09:52:51 +0000
Received: from localhost (localhost [127.0.0.1])
	by disroot.org (Postfix) with ESMTP id C266427561
	for <pgsql-admin@lists.postgresql.org>; Fri, 21 Feb 2020 10:52:42 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at disroot.org
Received: from knopi.disroot.org ([127.0.0.1])
	by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id J5bvvedlrZfa for <pgsql-admin@lists.postgresql.org>;
	Fri, 21 Feb 2020 10:52:41 +0100 (CET)
Date: Fri, 21 Feb 2020 10:55:14 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail;
	t=1582278761; bh=Ojl4UoPyxIMf9rulpE5RrGqjS88Xl1A05G+p/A6zgeA=;
	h=Date:From:To:Subject:In-Reply-To:References;
	b=FSO3/ODzod3+2eXLXT0znd/xs0dJIVisgjqnz0PaoNSITnE9xF0CgPScG+71QKUUn
	 K8rS5A0gJcy8AoueBns8LvFTJ0U/9aHOTO99NnAIMAUMsWQryKeE1BqRTBjQJuHp7p
	 KGQbaNSLNhbxg0Pkbmc1HJWWSWwI1DhqO67FbyvXnfTETQTJtjTioHTPNA0XcmawIl
	 xEAJjFy99PNXg/pLVQZIHb8j9ntohBWH44CGVUPaYtLL81N23OAtpn2o5Awrw4Y8sv
	 x0Sz6/POlwvSaQb4HULRz6J7UNj7so5yvtyYpq8DA08nyIFd4sn/6+uunl3Z9zTaAj
	 1WLkL2moOXRRA==
From: Jakub Olczyk <jwo@disroot.org>
To: pgsql-admin@lists.postgresql.org
Subject: Re: benchmarking proposed config
Message-ID: <20200221105514.084cb730@el-t490>
In-Reply-To: <1E6E0384-D13F-419E-ABC9-7BC52B001A68@killerbytes.com>
References: <1E6E0384-D13F-419E-ABC9-7BC52B001A68@killerbytes.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

Hi Scott,

On Thu, 20 Feb 2020 09:12:09 -0700
Scott Ribe <scott_ribe@killerbytes.com> wrote:

> Does anyone have suggestions for a utility that would easily let us
> mirror all queries to a "shadow" PG cluster, so that we can compare
> performance of our current production config against a new proposed
> config with our actual production traffic?

I am not sure if this would be an acceptable solution for you but there
is an open source utility called pgreplay[1]. Here is the description:

> pgreplay reads a PostgreSQL log file (*not* a WAL file), extracts the
> SQL statements and executes them in the same order and relative time
> against a PostgreSQL database cluster. 

This of course means that you'd need to have a fairly "chatty" log
configuration, but maybe it could work for your needs?


Cheers,
jwo


[1]: https://github.com/laurenz/pgreplay