Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ifWcX-0000rd-Sm for pgsql-docs@arkaria.postgresql.org; Thu, 12 Dec 2019 22:07:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ifWcW-0002nM-Nc for pgsql-docs@arkaria.postgresql.org; Thu, 12 Dec 2019 22:07:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ifWcW-0002mt-EH for pgsql-docs@lists.postgresql.org; Thu, 12 Dec 2019 22:07:40 +0000 Received: from smtp-fw-9102.amazon.com ([207.171.184.29]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ifWcS-0001uu-UD for pgsql-docs@lists.postgresql.org; Thu, 12 Dec 2019 22:07:39 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1576188457; x=1607724457; h=from:to:cc:subject:message-id:date:mime-version; bh=ANQura/GPgyAiUU4qlYb2L8QzuPyk4lDvCSpvHoyuFA=; b=Aj5rRiiLEDuxuB6jFyjar5cafzSC09F//cVUDVYIUmlfx1ngBPRRfn/h qSH/gRChyhi6dHX2Oovql45un9y3FULsU3F7mo+/f+BpeQsEzF3th5CH/ 2Sq5akX7dhDgeD8AJoDzIHX/Fx6KsYRsdRfkRgvyQ1rETya757WrriiJX o=; IronPort-SDR: /KrEDipi7lD03bkNPUAJBF4JlS+dOPkdd5VvXq2X4oYt8CHM7NE6LhArEYaSKMOgoYGdjZ3kzU 8dD+84CqN5qQ== X-IronPort-AV: E=Sophos;i="5.69,307,1571702400"; d="scan'208,217";a="13238916" Received: from sea32-co-svc-lb4-vlan3.sea.corp.amazon.com (HELO email-inbound-relay-1e-27fb8269.us-east-1.amazon.com) ([10.47.23.38]) by smtp-border-fw-out-9102.sea19.amazon.com with ESMTP; 12 Dec 2019 22:07:17 +0000 Received: from EX13MTAUWA001.ant.amazon.com (iad55-ws-svc-p15-lb9-vlan3.iad.amazon.com [10.40.159.166]) by email-inbound-relay-1e-27fb8269.us-east-1.amazon.com (Postfix) with ESMTPS id BBB35A222F; Thu, 12 Dec 2019 22:07:15 +0000 (UTC) Received: from EX13D18UWA002.ant.amazon.com (10.43.160.199) by EX13MTAUWA001.ant.amazon.com (10.43.160.58) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Thu, 12 Dec 2019 22:07:15 +0000 Received: from 186590ce269b.ant.amazon.com (10.43.162.222) by EX13D18UWA002.ant.amazon.com (10.43.160.199) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Thu, 12 Dec 2019 22:07:14 +0000 From: Jeremy Schneider To: "pgsql-www@postgresql.org" CC: , pgsql-general Subject: wait event docs Message-ID: Date: Thu, 12 Dec 2019 14:07:14 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------9025765581116A7B751F81F7" Content-Language: en-US X-Originating-IP: [10.43.162.222] X-ClientProxiedBy: EX13D25UWC003.ant.amazon.com (10.43.162.129) To EX13D18UWA002.ant.amazon.com (10.43.160.199) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --------------9025765581116A7B751F81F7 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit The wait event information in PostgreSQL is very helpful for troubleshooting.  I always reference the PostgreSQL docs first, and when people ask me about wait events that where I send them first.  The list of wait events there is comprehensive, but the descriptions are a bit terse and often use vocabulary that requires some familiarity with the internals to understand. AWS created some wait event documentation for Aurora with PostgreSQL compatibility which takes a slightly different approach.  It's a lot more words... but it tries to give useful suggestions about how to improve (or fix) the system when a particular wait event is encountered. https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Reference.html#AuroraPostgreSQL.Reference.Waitevents Something like this would be really valuable for open source PostgreSQL too.  While somebody's personal blog is one solution, it doesn't seem wholly inappropriate to live on a community resource.  I'd be happy to seed the content and continue making updates it as I regularly helping people solve problems on open source community PostgreSQL (and hopefully others contribute too). Could we create a new wiki page as a starting point, and we could draft up and maintain something there for a little while?  Maybe a place like https://wiki.postgresql.org/wiki/Wait_Events ? If it does turn out to be useful for a lot of people then maybe it could even get into the PG docs someday.  :) -Jeremy P.S. my wiki username is "Jer"  https://wiki.postgresql.org/wiki/User:Jer -- Jeremy Schneider Database Engineer Amazon Web Services --------------9025765581116A7B751F81F7 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: 8bit The wait event information in PostgreSQL is very helpful for troubleshooting.  I always reference the PostgreSQL docs first, and when people ask me about wait events that where I send them first.  The list of wait events there is comprehensive, but the descriptions are a bit terse and often use vocabulary that requires some familiarity with the internals to understand.

AWS created some wait event documentation for Aurora with PostgreSQL compatibility which takes a slightly different approach.  It's a lot more words... but it tries to give useful suggestions about how to improve (or fix) the system when a particular wait event is encountered.

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/AuroraPostgreSQL.Reference.html#AuroraPostgreSQL.Reference.Waitevents

Something like this would be really valuable for open source PostgreSQL too.  While somebody's personal blog is one solution, it doesn't seem wholly inappropriate to live on a community resource.  I'd be happy to seed the content and continue making updates it as I regularly helping people solve problems on open source community PostgreSQL (and hopefully others contribute too).

Could we create a new wiki page as a starting point, and we could draft up and maintain something there for a little while?  Maybe a place like https://wiki.postgresql.org/wiki/Wait_Events ?

If it does turn out to be useful for a lot of people then maybe it could even get into the PG docs someday.  :)

-Jeremy


P.S. my wiki username is "Jer"  https://wiki.postgresql.org/wiki/User:Jer


-- 
Jeremy Schneider
Database Engineer
Amazon Web Services
--------------9025765581116A7B751F81F7--