<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Partitioning on Development notes</title>
    <link>https://dev-pages.info/tags/partitioning/</link>
    <description>Recent content in Partitioning on Development notes</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Wed, 21 Dec 2016 07:08:59 +0000</lastBuildDate><atom:link href="https://dev-pages.info/tags/partitioning/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Partitioning in Relational databases</title>
      <link>https://dev-pages.info/partitioning-in-relational-databases/</link>
      <pubDate>Wed, 21 Dec 2016 07:08:59 +0000</pubDate>
      
      <guid>https://dev-pages.info/partitioning-in-relational-databases/</guid>
      <description>Introduction Partitioning is a process of dividing a table into multiple smaller pieces, where each piece of such a database object is called a partition. This tutorial describes what is Partitioning and provided an example of Range partitioning in PostgreSQL database.
Benefits of partitioning Query performance could be increased when: most of the heavily accessed rows of the table are in a single partition or a small number of partitions. queries or updates access a large percentage of a single partition because of sequential scan of that partition instead of using an index and random access reads scattered across the whole table Seldom-used data can be migrated to cheaper and slower storage media Performing maintenance operations on one or more partitions can be made more quickly.</description>
    </item>
    
  </channel>
</rss>
