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 1ifeme-0001Fo-TS for pgsql-docs@arkaria.postgresql.org; Fri, 13 Dec 2019 06:50:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ifemd-0006ZU-Ob for pgsql-docs@arkaria.postgresql.org; Fri, 13 Dec 2019 06:50:39 +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 1ifemc-0006ZN-Qx for pgsql-docs@lists.postgresql.org; Fri, 13 Dec 2019 06:50:39 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ifemY-0006wL-Mn for pgsql-docs@lists.postgresql.org; Fri, 13 Dec 2019 06:50:38 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 3D96B22766; Fri, 13 Dec 2019 01:50:33 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 13 Dec 2019 01:50:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=TVp0qF6g6RelBnG9JSGjh+qe2vy Ua0PTbX3glWVxyqY=; b=Fg9pbYEQ5M9ybuPXZbC1eiBDnYtNVfC5u1oMJ0AeWfO PMNCZ839iM9t07dvFSoEgCWn9vvqzeLXRR9iwP4kXnGQRFNreQ3qGkQsSKsxKuia 9XfNn+AOCS0CgjIsYKOgmqtZTDysZbhdiOIRYg7qFLEbC85nZB0yx+/veQmmDq7B 783eFiqtfyW7SRNOsoTyN8odMTN1U1Tr1M4u+P8v7/uMWMBaItGOMNoGlC6ongQl ZaCbEV7ub7P6NK/ig523CqbyGJ/Z1TIfnZfZUucf+lK0CQLYYXg08mawO31HoVO5 +eVYz6hx3eGIXQfRuDUfR+rtqKgf1/IjLZe5eCxQyiA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=TVp0qF 6g6RelBnG9JSGjh+qe2vyUa0PTbX3glWVxyqY=; b=u7ccfgHwSs+qoOuQbLYONX D4bTSR9h/NEtB1x+7HQSG9IKqKvOBfiFXYqr05AwUm8ZJULpnZzYEhj3LLalUMl+ an6iWD/gqc06SC8c3jf4ijpcpHFZXZgCvtdGnIIfDQklhcqt6tjbONZQIKBBPp3d 3SHvaf93nVDrDINXobJ4R7kqbaEXuC6pUsJYTWhoPxDgktPSjLA2T1Wl9A0Meg3H u1wZPJWude/om/5dU8afnNIt3N4i/vzp4/Nqr1kL4cbiHbNtruT9oh+p7BCfvBQW ilCSdN8xfaBe/pk6IJn3xvl53N8l11X9gpMxaFWVJ8QMFUfoH2wIMrl5qJaB9HJQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudelkedgleelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlfeehmdenucfjughrpeffhffvuffkfhggtggujgesghdtreertddt udenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgnecu kfhppeduuddurddutddvrddukedtrddukeehnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hmihgthhgrvghlsehprghquhhivghrrdighiiinecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from paquier.xyz (ee0822lan1.rev.em-net.ne.jp [111.102.180.185]) by mail.messagingengine.com (Postfix) with ESMTPA id EB30C3060134; Fri, 13 Dec 2019 01:50:31 -0500 (EST) Date: Fri, 13 Dec 2019 15:50:29 +0900 From: Michael Paquier To: Jeremy Schneider Cc: pgsql-docs@lists.postgresql.org Subject: Re: wait event docs Message-ID: <20191213065029.GF1942@paquier.xyz> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="CEUtFxTsmBsHRLs3" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --CEUtFxTsmBsHRLs3 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 12, 2019 at 02:07:14PM -0800, Jeremy Schneider wrote: > The wait event information in PostgreSQL is very helpful for > troubleshooting.=A0 I always reference the PostgreSQL docs first, and when > people ask me about wait events that where I send them first.=A0 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. (I think that it would be better to avoid cross-posting among multiple lists. Please note that I have removed -www and -general in my reply, keeping -docs because that7s the most meaningful) > Could we create a new wiki page as a starting point, and we could draft > up and maintain something there for a little while?=A0 Maybe a place like > https://wiki.postgresql.org/wiki/Wait_Events ? That sounds like a good idea, as it is true that the docs are rather sparse about the meaning behind a given wait event showing a lot in profiles and what it actually means for your application. We have a couple of links from the docs to the wiki, so it could be an idea to add a link to the wiki in the docs near the wait event table. more to the point, this makes me wonder if actually a better place for such stuff would be a new section dedicated to wait event profiles here: https://www.postgresql.org/docs/devel/monitoring.html -- Michael --CEUtFxTsmBsHRLs3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl3zNLUACgkQnvQgOdby QH1bMQ//WHvNbQJZcVp1hKrPpMJxxuktA6kZeZ9TGIHJC0nv9QGngR9MY7s6zXAD Omon8775ASCRrkPhALavkuXpaRT8+qg06q0fRFMdugY/YSv6oOZ5LwsIybAjAi+K Nrb4sbi0/p1fxMJxVik8sLpRBcyc7QjEKTDon/ArtQy/u5F5sy0r+Ve3picJBySg 3X4JDGfnWl4bipBa8nzqTfpYZEPJmgU7jicShhYVcRPULfWv62T57K9XVtOzGfHB sEI3thWzpBAg0DSGKEDNywvnOWMWkoKcGMpwOevnAEK5TPEkuj7oWbNeK2MSD/IK HPKv79mBPr8vFHBrhk/GyaqA/17sfIGO6bkkpVManfF5wxMQyD3X153kB2Yoky+7 g+f0UhbQCH8oPNbI9DmsEHiE7TT0ZAiUKNCl21FAh2Oq3w8iCaJncxmoss/X1k9H et9aTg9BV9J25JjNXhcxJrgGB2vqtMKOMIIYiIPVq+f3oF6G9lh1mfPsGXLNKV/N 42noKbsk+75OycZcI6zyFWIRQYk5dYVgHqDzM44ED1LmEFhyEE46FMOSPsBRSUyy BbyfU4lmPhSm4Z5dgXhRSslXsU00a6g142jZqCGlY2uC5gBK8k/U04StGWAPd1SW 6bTGDfqO6lUdV/rfPDMyof4g/cMUBqKezyPPA/3fQOdBb+HXAak= =qXSM -----END PGP SIGNATURE----- --CEUtFxTsmBsHRLs3--