From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: impact pgbench on a physical replicated stream
Date: Fri, 28 Jul 2023 09:50:21 -0500
Message-ID: <63dab46e-fd38-7f65-54e0-bb3c67346300@gmail.com> (raw)
In-Reply-To: <CAG7ytiuttdLgGyQAF2JNmHMxLjCcr0WE4yaoONDkak=W2nwUNw@mail.gmail.com>
References: <CAG7ytiuttdLgGyQAF2JNmHMxLjCcr0WE4yaoONDkak=W2nwUNw@mail.gmail.com>
On 7/28/23 07:20, Gert Cuykens wrote:
> Hi, I would like to pgbench the production postgres that is being physical
> replicated to a slave. Will I shoot myself in the foot because of the
> physical replication if I try pgbench on prodcution postgres.
Replication or not, why are you running pgbench on a *production* server?
And by "shoot myself in the foot", are you asking whether it would overwhelm
some system or another, thereby breaking replication? If so, we can't
answer that, since we don't know the hardware specifications, your current
workload, and whether or not you're doing synchronous or asynchronous
replication.
--
Born in Arizona, moved to Babylonia.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: impact pgbench on a physical replicated stream
In-Reply-To: <63dab46e-fd38-7f65-54e0-bb3c67346300@gmail.com>
References: <CAG7ytiuttdLgGyQAF2JNmHMxLjCcr0WE4yaoONDkak=W2nwUNw@mail.gmail.com> <63dab46e-fd38-7f65-54e0-bb3c67346300@gmail.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