pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
impact pgbench on a physical replicated stream
3+ messages / 2 participants
[nested] [flat]

* impact pgbench on a physical replicated stream
@ 2023-07-28 12:20  Gert Cuykens <gert.cuykens@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Gert Cuykens @ 2023-07-28 12:20 UTC (permalink / raw)
  To: pgsql-general@lists.postgresql.org

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.
Thanks

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: impact pgbench on a physical replicated stream
@ 2023-07-28 14:50  Ron <ronljohnsonjr@gmail.com>
  parent: Gert Cuykens <gert.cuykens@gmail.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Ron @ 2023-07-28 14:50 UTC (permalink / raw)
  To: pgsql-general@lists.postgresql.org

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.

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: impact pgbench on a physical replicated stream
@ 2023-07-28 16:32  Gert Cuykens <gert.cuykens@gmail.com>
  parent: Ron <ronljohnsonjr@gmail.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Gert Cuykens @ 2023-07-28 16:32 UTC (permalink / raw)
  To: Ron <ronljohnsonjr@gmail.com>; +Cc: pgsql-general@lists.postgresql.org

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@gmail.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.
>

^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2023-07-28 16:32 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-07-28 12:20 impact pgbench on a physical replicated stream Gert Cuykens <gert.cuykens@gmail.com>
2023-07-28 14:50 ` Ron <ronljohnsonjr@gmail.com>
2023-07-28 16:32   ` Gert Cuykens <gert.cuykens@gmail.com>

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