Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qPOnV-00Atmj-2v for pgsql-general@arkaria.postgresql.org; Fri, 28 Jul 2023 14:50:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qPOnT-00GpRc-65 for pgsql-general@arkaria.postgresql.org; Fri, 28 Jul 2023 14:50:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qPOnS-00GpRQ-Rf for pgsql-general@lists.postgresql.org; Fri, 28 Jul 2023 14:50:26 +0000 Received: from mail-yw1-x1134.google.com ([2607:f8b0:4864:20::1134]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qPOnQ-000ts0-JW for pgsql-general@lists.postgresql.org; Fri, 28 Jul 2023 14:50:26 +0000 Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-583b019f1cbso22621167b3.3 for ; Fri, 28 Jul 2023 07:50:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690555822; x=1691160622; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=xP2ISEpHIVFhd2OLOkYFfdIA8W3UQrLcAIZ5isfIdk4=; b=WKC0aBtI+N0Iz6qn67Vy1UghlcHARKukb2pkvbzIP4Q52SaaZ2/G59mA8JXuKI6A+8 fZgbFBI8EE6DIyB0sjIOnSPnzz46MG2Vvadi8UHSlyjuxcO/SrZJcf41sKLttE3mZi5l RtbpNPYf+XWHkeqHkxMaaK+SjGeK51wCJgTZh09J8r8v6MJLQqeT47ebUNiACGFdpiuY ghVAiwvYjSRYPsU62JdAJ1/ZGM8/pO7b/YaLuVQ09sK/H1ofAAnbST3Fw6wib2IR8VMt g0iAFw37AMqE5Zkr31p3VNcEL8I3hToBkcSdYzV/k8qOsV/Pz/XBqZ6yZ+JYKeVdFyn3 5BQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690555822; x=1691160622; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=xP2ISEpHIVFhd2OLOkYFfdIA8W3UQrLcAIZ5isfIdk4=; b=XqfylmU+4zeTXHgR4KB5Fcjib3hG0XzLpn2ahQX5e87HQ06D6jRp6FnUoiL/kwV5Z9 8HRHDCL9d+Sfh7bKMRilSOhyhDQ3bqNNpalEgyCImhFiCfjq+1t8rSqQcT1qCqv3zYE7 Cy1J6pMboz0jbkdh30EnXkkMpaEfOjEAYLPtpihZ1VzS8HE898M+DNe/hPC2eQNGmJu8 0ni1Q4E3nL6o5eg3iAmCjUcLugF+w+Nru6QQMS6g73dBQHFLbwUI029gWFGnPoyhn5ws Wy/sffFBDZowa1BDPYcndq5pVtAlzzgV7auIX//Y5m6S/GXffRSMPxVO0Co51Cmgmeg0 acnA== X-Gm-Message-State: ABy/qLawgCjE0qDhAfnofFZOzTeusvLxbW3uPCIvBtkn8rXMmoiC/MIO rTLAGNknyjMpCnPYuUbZm3ZxpIFywMM= X-Google-Smtp-Source: APBJJlG4hQC/Wi06Djy8hnixGjuvoRLJFFQMtoedwbLzQO9gY22GcKpWvBfjCmBuGHfNAFul4V7R6g== X-Received: by 2002:a81:69d5:0:b0:55d:a9d7:521e with SMTP id e204-20020a8169d5000000b0055da9d7521emr2043739ywc.18.1690555822103; Fri, 28 Jul 2023 07:50:22 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:c11c:5df6:9acb:ecd1? ([2600:1700:bd2c:b810:c11c:5df6:9acb:ecd1]) by smtp.googlemail.com with ESMTPSA id d79-20020a814f52000000b00583e52232f1sm1083096ywb.112.2023.07.28.07.50.21 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 28 Jul 2023 07:50:21 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------0fJ8CE00ZNzlso4uY5c2DDsH" Message-ID: <63dab46e-fd38-7f65-54e0-bb3c67346300@gmail.com> Date: Fri, 28 Jul 2023 09:50:21 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: impact pgbench on a physical replicated stream Content-Language: en-US To: pgsql-general@lists.postgresql.org References: From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------0fJ8CE00ZNzlso4uY5c2DDsH Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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. --------------0fJ8CE00ZNzlso4uY5c2DDsH Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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.
--------------0fJ8CE00ZNzlso4uY5c2DDsH--