{"id":8825,"date":"2022-04-03T14:17:58","date_gmt":"2022-04-03T19:17:58","guid":{"rendered":"https:\/\/www.rushworth.us\/lisa\/?p=8825"},"modified":"2022-04-20T00:08:27","modified_gmt":"2022-04-20T05:08:27","slug":"postgresql-querying-hot-standby-server","status":"publish","type":"post","link":"https:\/\/www.rushworth.us\/lisa\/?p=8825","title":{"rendered":"Postgresql – Querying Hot Standby Server"},"content":{"rendered":"

We hit our maximum connection limit on some PostgreSQL servers — which made me wonder why the hot standby servers weren’t being used … well, at all. They’re equally big, expensive servers with loads<\/em> of disk space. But they’re just sitting there “in case”.<\/p>\n

So we directed some traffic over to the standby server. I’m also going to tweak a few settings related to user limits — increase the max connections since these are dedicated hosts and have plenty of available I\/O, memory, CPU, etc resources; increase the number of reserved connections since replication filled up all of the reserved slots; implement a per-user connection limit on one account that runs a lot<\/em> of threads — but directing some people who were only trying to look at data over to the standby server seemed like a quick fix.<\/p>\n

Now, we discovered something interesting about how queries against the standby interact with replication. It makes a lot of sense when you start thinking about it — if you query against the writable replica, there’s some blocking that goes on. The system isn’t going to vacuum data that you’re currently trying to use. The standby, however, doesn’t have any way to clue the writable replica in to the fact you are<\/em> trying to use some data. So the writable replica gets a delete, does its thing to hide those rows from future queries, and eventually auto-vacuum comes through and cleans up those rows. All of this gets pushed over to the standby … and there goes the data you were trying to read.<\/p>\n

Odds of this happening on a query that takes eight seconds? Incredibly low! Odds increase, however, the longer a query runs. So some of our super massive reports started seeing an error indicating that their query was cancelled “due to a conflict with recovery”<\/p>\n

\"\"<\/a><\/p>\n

There are two solutions in the PostgreSQL documentation<\/a> — one is to increase the max_standby_streaming_delay<\/tt> value (there’s also an archive delay, but we aren’t particularly concerned about clients querying the server during recovery operations) the other is to avoid vacuuming data too quickly — either by setting hot_standby_feedback<\/tt> on the standby or increasing vacuum_defer_cleanup_age<\/tt> on the primary.<\/p>\n

There’s a third option too — don’t use the standby for long-running queries. That’s easily done in our case … and doesn’t require tweaking any PostgreSQL settings. Ad hoc reporting and direct user access really shouldn’t<\/em> be implementing such substantial queries (it’s always good to have a SQL expert plan out and optimize complex queries if that’s an option).<\/p>\n","protected":false},"excerpt":{"rendered":"

We hit our maximum connection limit on some PostgreSQL servers — which made me wonder why the hot standby servers weren’t being used … well, at all. They’re equally big, expensive servers with loads of disk space. But they’re just sitting there “in case”. So we directed some traffic over to the standby server. I’m …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1522],"tags":[1577,1349,1580,1579,1578],"class_list":["post-8825","post","type-post","status-publish","format-standard","hentry","category-postgresql","tag-load-balancing","tag-postgresql","tag-postgresql-replication","tag-replaying-wal","tag-wal"],"_links":{"self":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/8825","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=8825"}],"version-history":[{"count":1,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/8825\/revisions"}],"predecessor-version":[{"id":8827,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=\/wp\/v2\/posts\/8825\/revisions\/8827"}],"wp:attachment":[{"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=8825"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=8825"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rushworth.us\/lisa\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=8825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}