<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CTE on BonesMoses.org</title>
    <link>https://bonesmoses.org/tags/cte/</link>
    <description>Recent content in CTE on BonesMoses.org</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 20 Jan 2017 14:06:32 +0000</lastBuildDate><atom:link href="https://bonesmoses.org/tags/cte/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PG Phriday: Everything in Common</title>
      <link>https://bonesmoses.org/2017/pg-phriday-everything-in-common/</link>
      <pubDate>Fri, 20 Jan 2017 14:06:32 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2017/pg-phriday-everything-in-common/</guid>
      <description>Not a lot of people remember what Postgres was like before version 8.4. In many ways, this was the first &amp;ldquo;modern&amp;rdquo; release of the database engine. CTEs, Window Functions, column level permissions, in-place upgrade compatible with subsequent versions, collation support, continuous query statistic collection; it was just a smorgasbord of functionality.
Of these, CTEs or Common Table Expressions, probably enjoy the most user-level exposure; for good reason. Before this, there was no way to perform a recursive query in Postgres, which really hurts in certain situations.</description>
    </item>
    
    <item>
      <title>PG Phriday: Instant Runoff Through SQL</title>
      <link>https://bonesmoses.org/2016/pg-phriday-instant-runoff-through-sql/</link>
      <pubDate>Fri, 11 Nov 2016 14:47:41 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2016/pg-phriday-instant-runoff-through-sql/</guid>
      <description>The United States held an election recently, and there has been some &amp;hellip; mild controversy regarding the results. Many raised issues about this before the election itself, but what if we had used instant-runoff voting instead? More importantly, can we implement it with Postgres?
Well, the answer to the last question is a strong affirmative. So long as we don&amp;rsquo;t break the results down into voting districts, and make wild unsupported assumptions regarding rankings, that is.</description>
    </item>
    
    <item>
      <title>Trumping the PostgreSQL Query Planner</title>
      <link>https://bonesmoses.org/2014/trumping-the-postgresql-query-planner/</link>
      <pubDate>Thu, 08 May 2014 12:24:45 +0000</pubDate>
      
      <guid>https://bonesmoses.org/2014/trumping-the-postgresql-query-planner/</guid>
      <description>With the release of PostgreSQL 8.4, the community gained the ability to use CTE syntax. As such, this is a fairly old feature, yet it&amp;rsquo;s still misunderstood in a lot of ways. At the same time, the query planner has been advancing incrementally since that time. Most recently, PostgreSQL has gained the ability to perform index-only scans, making it possible to fetch results straight from the index, without confirming rows with the table data.</description>
    </item>
    
  </channel>
</rss>
