From: | Gert Cuykens <gert(dot)cuykens(at)gmail(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: impact pgbench on a physical replicated stream |
Date: | 2023-07-28 16:32:58 |
Message-ID: | CAG7ytiuTX6GJ3zJ1+T6z=yJAbSqBALOSicXTNos3S-Fv8812Wg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Using asynchronous replication. Production is running on a gaming PC at the
moment because it was to slow on a state of the art hypervisor 128 core 1TB
mem and nvme disk server rack... (where de replicated slave is running on)
I would like to know what number this gaming pc is pulling that supposedly
the server rack can't.
On Fri, Jul 28, 2023 at 4:50 PM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
> 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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-07-28 17:29:32 | Re: Bogus temp file reporting? |
Previous Message | Tom Lane | 2023-07-28 15:01:04 | Re: AW: Compile static postgres.lib for postgres 15.3 on Windows |