<commit_before>---
layout: post
title:  "Highlighting Postgres 10 new features: Logical Replication and Partitioning."
date:   2017-02-18
description: And playing with retention policies.
tags : [PostgreSQL, Sharding, Partitioning, LogicalReplication]
categories:
- PostgreSQL
permalink: postgres10logrepypart
comments: true 
---


Heya! I this article we are going to explore two of the major features commited in 
the upcoming PostgreSQL release: Logical Replication and Partitioning. Needeless to 
say that these features aren't yet available in the stable release, so they are prune
to change or extended.

The current article is just a sneak peak of the upcoming talk _Demystifying Logical
Replication on PostgreSQL_ at [Percona Live Santa Clara 2017][4]. Get your tickets!

## Logical Replication

The current logical replication mechanism is a row based decoding, which defers on
those techniques based on _statement_ in which no matter how many rows are involved
on the source query, they will be shipped as individual rows into the slaves.

This is something you may want to have in consideration when doing bulk loads, as there
are other tools which can be a better fit than streaming everything from the master.

Generally speaking, it consist in three _visible_ elements:

- a Publication  (source)<commit_msg>Fixing disqus and moving posts<commit_after>---
layout: post
title:  "Highlighting Postgres 10 new features: Logical Replication and Partitioning."
date:   2017-02-18
description: And playing with retention policies.
tags : [PostgreSQL, Sharding, Partitioning, LogicalReplication]
categories:
- PostgreSQL
category: blog
comments: true 
permalink: postgres10logrepypart
---


Heya! I this article we are going to explore two of the major features commited in 
the upcoming PostgreSQL release: Logical Replication and Partitioning. Needeless to 
say that these features aren't yet available in the stable release, so they are prune
to change or extended.

The current article is just a sneak peak of the upcoming talk _Demystifying Logical
Replication on PostgreSQL_ at [Percona Live Santa Clara 2017][4]. Get your tickets!

## Logical Replication

The current logical replication mechanism is a row based decoding, which defers on
those techniques based on _statement_ in which no matter how many rows are involved
on the source query, they will be shipped as individual rows into the slaves.

This is something you may want to have in consideration when doing bulk loads, as there
are other tools which can be a better fit than streaming everything from the master.

Generally speaking, it consist in three _visible_ elements:

- a Publication  (source)
{'fraction_non_alphanumeric': 0.040732436472346784, 'fraction_numerical': 0.012705530642750373, 'mean_word_length': 4.883516483516484, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6641762', 'n_tokens_mistral': 714, 'n_tokens_neox': 668, 'n_words': 381}