Postgres replication delay with inserts into large table

Apex Framework / library for consuming REST services

Is there a hemisphere-neutral way of specifying a season?

Method Does Not Exist error message

Can my sorcerer use a spellbook only to collect spells and scribe scrolls, not cast?

Why was the shrinking from 8″ made only to 5.25″ and not smaller (4″ or less)?

ssTTsSTtRrriinInnnnNNNIiinngg

How much of data wrangling is a data scientist's job?

Can the Meissner effect explain very large floating structures?

What is the idiomatic way to say "clothing fits"?

Do scales need to be in alphabetical order?

Can I run a new neutral wire to repair a broken circuit?

What reasons are there for a Capitalist to oppose a 100% inheritance tax?

Can compressed videos be decoded back to their uncompresed original format?

Why didn't Boeing produce its own regional jet?

Expand and Contract

How dangerous is XSS?

What is the most common color to indicate the input-field is disabled?

What's the in-universe reasoning behind sorcerers needing material components?

Unable to supress ligatures in headings which are set in Caps

Cursor Replacement for Newbies

How to tell a function to use the default argument values?

Can a virus destroy the BIOS of a modern computer?

Determining Impedance With An Antenna Analyzer

Why would the Red Woman birth a shadow if she worshipped the Lord of the Light?



Postgres replication delay with inserts into large table














0















I have a large table (over 35 million rows, most rows contain TOAST'd columns) that I've isolated as the source of growing replication delays in my Postgres instance. When I'm doing inserts into this table (at a rate of 100s per second) I see the replication delay, both in time and bytes, grow. The only way I get the replication delay to come back down is to either stop doing inserts into this table or truncate this table and allow the inserts to proceed. Based on my testing this issue seems to pop up somewhere in the neighborhood of 30 million rows, and not before.



To give you an idea of volume, I'm normally shipping about 200 MB/s of xlogs to the replica, have already tested and verified I can do over 1 GB/s when this table is not an issue, so I know it's not a network problem.



Any ideas as to why this happens and what I can do to address it? Thanks to a previous round of trying to address this problem I've already turned on wal compression and use replication slots now.









share



























    0















    I have a large table (over 35 million rows, most rows contain TOAST'd columns) that I've isolated as the source of growing replication delays in my Postgres instance. When I'm doing inserts into this table (at a rate of 100s per second) I see the replication delay, both in time and bytes, grow. The only way I get the replication delay to come back down is to either stop doing inserts into this table or truncate this table and allow the inserts to proceed. Based on my testing this issue seems to pop up somewhere in the neighborhood of 30 million rows, and not before.



    To give you an idea of volume, I'm normally shipping about 200 MB/s of xlogs to the replica, have already tested and verified I can do over 1 GB/s when this table is not an issue, so I know it's not a network problem.



    Any ideas as to why this happens and what I can do to address it? Thanks to a previous round of trying to address this problem I've already turned on wal compression and use replication slots now.









    share

























      0












      0








      0








      I have a large table (over 35 million rows, most rows contain TOAST'd columns) that I've isolated as the source of growing replication delays in my Postgres instance. When I'm doing inserts into this table (at a rate of 100s per second) I see the replication delay, both in time and bytes, grow. The only way I get the replication delay to come back down is to either stop doing inserts into this table or truncate this table and allow the inserts to proceed. Based on my testing this issue seems to pop up somewhere in the neighborhood of 30 million rows, and not before.



      To give you an idea of volume, I'm normally shipping about 200 MB/s of xlogs to the replica, have already tested and verified I can do over 1 GB/s when this table is not an issue, so I know it's not a network problem.



      Any ideas as to why this happens and what I can do to address it? Thanks to a previous round of trying to address this problem I've already turned on wal compression and use replication slots now.









      share














      I have a large table (over 35 million rows, most rows contain TOAST'd columns) that I've isolated as the source of growing replication delays in my Postgres instance. When I'm doing inserts into this table (at a rate of 100s per second) I see the replication delay, both in time and bytes, grow. The only way I get the replication delay to come back down is to either stop doing inserts into this table or truncate this table and allow the inserts to proceed. Based on my testing this issue seems to pop up somewhere in the neighborhood of 30 million rows, and not before.



      To give you an idea of volume, I'm normally shipping about 200 MB/s of xlogs to the replica, have already tested and verified I can do over 1 GB/s when this table is not an issue, so I know it's not a network problem.



      Any ideas as to why this happens and what I can do to address it? Thanks to a previous round of trying to address this problem I've already turned on wal compression and use replication slots now.







      postgresql replication postgresql-11





      share












      share










      share



      share










      asked 1 min ago









      G Gordon Worley IIIG Gordon Worley III

      1215




      1215






















          0






          active

          oldest

          votes












          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "182"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f233894%2fpostgres-replication-delay-with-inserts-into-large-table%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Database Administrators Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f233894%2fpostgres-replication-delay-with-inserts-into-large-table%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Anexo:Material bélico de la Fuerza Aérea de Chile Índice Aeronaves Defensa...

          Always On Availability groups resolving state after failover - Remote harden of transaction...

          update json value to null Announcing the arrival of Valued Associate #679: Cesar Manara ...