<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Jeremy Schneider</title>
    <description></description>
    <link>https://speakerdeck.com/ardentperf</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/ardentperf.rss"/>
    <lastBuildDate>2019-09-20 15:18:17 -0400</lastBuildDate>
    <item>
      <title>Wait! What’s going on inside my database?</title>
      <description>PostgreSQL 9.6 introduced wait events and PostgreSQL 10 progressed them, but what are they? What do they mean? How do I find them and how do I make them go away? Wait events are one of the most significant advancements in observability for PostgreSQL databases; their usefulness is unparalleled in troubleshooting performance. This talk will go into all that and more as we explore the world of PostgreSQL wait events. </description>
      <media:content url="https://files.speakerdeck.com/presentations/0f22e8b001104f8084dfa795ed25e512/preview_slide_0.jpg?13650565" type="image/jpeg" medium="image"/>
      <content:encoded>PostgreSQL 9.6 introduced wait events and PostgreSQL 10 progressed them, but what are they? What do they mean? How do I find them and how do I make them go away? Wait events are one of the most significant advancements in observability for PostgreSQL databases; their usefulness is unparalleled in troubleshooting performance. This talk will go into all that and more as we explore the world of PostgreSQL wait events. </content:encoded>
      <pubDate>Thu, 19 Sep 2019 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/ardentperf/wait-whats-going-on-inside-my-database</link>
      <guid>https://speakerdeck.com/ardentperf/wait-whats-going-on-inside-my-database</guid>
    </item>
  </channel>
</rss>
