<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/https/speakerdeck.com/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>Melanie</title>
    <description/>
    <link>https://speakerdeck.com/melanieplageman</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/melanieplageman.rss"/>
    <lastBuildDate>2020-05-19 21:48:31 -0400</lastBuildDate>
    <item>
      <title>Making your patch more committable</title>
      <description>What to do and not to do to make your Postgres patch more committable.</description>
      <media:content url="https://files.speakerdeck.com/presentations/6ad256b0b4c54f90a091727a2ebe17a7/preview_slide_0.jpg?28283821" type="image/jpeg" medium="image"/>
      <content:encoded>What to do and not to do to make your Postgres patch more committable.</content:encoded>
      <pubDate>Thu, 21 Dec 2023 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/melanieplageman/making-your-patch-more-committable</link>
      <guid>https://speakerdeck.com/melanieplageman/making-your-patch-more-committable</guid>
    </item>
    <item>
      <title>intro to benchmarking with pgbench</title>
      <description></description>
      <media:content url="https://files.speakerdeck.com/presentations/c9d2137d7d4d457eb7b5d95f6dac5622/preview_slide_0.jpg?27327444" type="image/jpeg" medium="image"/>
      <content:encoded></content:encoded>
      <pubDate>Mon, 09 Oct 2023 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/melanieplageman/intro-to-benchmarking-with-pgbench</link>
      <guid>https://speakerdeck.com/melanieplageman/intro-to-benchmarking-with-pgbench</guid>
    </item>
    <item>
      <title>Visualizing Postgres I/O Performance for Development</title>
      <description></description>
      <media:content url="https://files.speakerdeck.com/presentations/f6eb467e19c74d7c80f7c4b6de3b0392/preview_slide_0.jpg?25976266" type="image/jpeg" medium="image"/>
      <content:encoded></content:encoded>
      <pubDate>Mon, 12 Jun 2023 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/melanieplageman/o-performance-for-development</link>
      <guid>https://speakerdeck.com/melanieplageman/o-performance-for-development</guid>
    </item>
    <item>
      <title>Additional I/O Observability with pg_stat_io</title>
      <description></description>
      <media:content url="https://files.speakerdeck.com/presentations/3b558b45f2a441d58930e1745766a797/preview_slide_0.jpg?25296301" type="image/jpeg" medium="image"/>
      <content:encoded></content:encoded>
      <pubDate>Tue, 18 Apr 2023 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/melanieplageman/o-observability-with-pg-stat-io</link>
      <guid>https://speakerdeck.com/melanieplageman/o-observability-with-pg-stat-io</guid>
    </item>
    <item>
      <title>work_mem warriors</title>
      <description>Teaching HashAgg, HashJoin, and Other Memory-Intensive Operators to Respect work_mem's Boundaries.

Recent work on the Postgres executor has made improvements to memory management -- from accounting for the memory used to responding to memory pressure. It is important to bind the memory usage of the database with the appropriate execution mechanisms and to choose those during planning based on cost in order to meet users' expectations and ensure predictable performance.

This talk will cover three such improvements: the addition of memory accounting information to MemoryContexts, the memory-bounding of HashAgg (spilling HashAgg to disk), and the adaptive hashjoin fallback to nested hashloop join.

Presenters: Jeff Davis and Melanie Plageman</description>
      <media:content url="https://files.speakerdeck.com/presentations/9457dec6fe2f48449ddcb5554263da4c/preview_slide_0.jpg?15547157" type="image/jpeg" medium="image"/>
      <content:encoded>Teaching HashAgg, HashJoin, and Other Memory-Intensive Operators to Respect work_mem's Boundaries.

Recent work on the Postgres executor has made improvements to memory management -- from accounting for the memory used to responding to memory pressure. It is important to bind the memory usage of the database with the appropriate execution mechanisms and to choose those during planning based on cost in order to meet users' expectations and ensure predictable performance.

This talk will cover three such improvements: the addition of memory accounting information to MemoryContexts, the memory-bounding of HashAgg (spilling HashAgg to disk), and the adaptive hashjoin fallback to nested hashloop join.

Presenters: Jeff Davis and Melanie Plageman</content:encoded>
      <pubDate>Wed, 27 May 2020 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/melanieplageman/work-mem-warriors</link>
      <guid>https://speakerdeck.com/melanieplageman/work-mem-warriors</guid>
    </item>
  </channel>
</rss>
