From: John Scalia <jayknowsunix@gmail.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Creating a materialized view causing blocks
Date: Wed, 30 Dec 2020 16:38:31 -0500
Message-ID: <52BF172F-FF9F-4DAC-A9E4-A540D3E84D5E@gmail.com> (raw)
Over last evening, one of my colleagues had begun recreating a materialized view. From looking at his code, it was only doing some selects, like one would expect, however, several API clients ended up being blocked by this, and I’m attempting to understand why. I should note that a couple of the tables used here, contained more than 100 million rows, and I’m wondering if the system simply gave up trying to keep the view’s data consistency on par, and if a more than a non-exclusive read block was then imposed. The API’s involved basically kept getting respawned, and at one point there were more than 4000 attempted simultaneous connections. Not a lot of fun, but fortunately for me, the application team only called the other DBA to fix the issue. I’d still like to know what happened.
—
Jay
Sent from my iPad
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jayknowsunix@gmail.com
Subject: Re: Creating a materialized view causing blocks
In-Reply-To: <52BF172F-FF9F-4DAC-A9E4-A540D3E84D5E@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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