performance Archives - Page 3 of 4 - 2ndQuadrant

Posts

Parallel Aggregate – Getting the most out of your CPUs

March 21, 2016/10 Comments/in David's PlanetPostgreSQL /by David Rowley

A small peek into the future of what should be arriving for PostgreSQL 9.6. Today PostgreSQL took a big step ahead in the data warehouse world and we now are able to perform aggregation in parallel using multiple worker processes! This is great news for those of you who are running large aggregate queries over […]

Tables and indexes vs. HDD and SSD

March 17, 2016/3 Comments/in 2ndQuadrant, PostgreSQL, Tomas' PlanetPostgreSQL /by Tomas Vondra

Although in the future most database servers (particularly those handling OLTP-like workloads) will use a flash-based storage, we’re not there yet – flash storage is still considerably more expensive than traditional hard drives, and so many systems use a mix of SSD and HDD drives. That however means we need to decide how to split […]

Postgres-XL 9.5R1Beta1 is here!

February 18, 2016/1 Comment/in 2ndQuadrant, Pavan's PlanetPostgreSQL /by Pavan Deolasee

I’m extremely pleased to see that after months of efforts and contributions by different people around the world, Postgres-XL 9.5 R1 Beta1 has finally arrived. This release is significantly better, in all respects such as performance, stability and high availability, as compared to the past release. Enormous amount of work has gone into PostgreSQL in the […]

Postgres-XL: Dealing with read-only transactions

February 12, 2016/3 Comments/in 2ndQuadrant, Pavan's PlanetPostgreSQL /by Pavan Deolasee

One of the problems with Postgres-XL 9.2 is that it assigns a global transaction identifier (GXID) for every transaction that is started in the cluster. Since its hard for the system to know if a transaction is read-only or not (remember, even SELECT queries can do write activities), Postgres-XL would always assign a GXID and send […]

PgBouncer 1.7 – “Colors Vary After Resurrection”

February 3, 2016/7 Comments/in 2ndQuadrant, Gulcin's PlanetPostgreSQL, PostgreSQL /by Gulcin Yildirim

PgBouncer is a lightweight connection pooler for PostgreSQL. PgBouncer 1.7 was announced on the 18th of December 2015. In this blog post we’ll talk about the major new improvements in PgBouncer.

Performance limits of logical replication solutions

January 20, 2016/6 Comments/in 2ndQuadrant, pglogical, PostgreSQL, Tomas' PlanetPostgreSQL /by Tomas Vondra

In the previous blog post, I briefly explained how we got the performance numbers published in the pglogical announcement. In this blog post I’d like to discuss the performance limits of logical replication solutions in general, and also how they apply to pglogical. physical replication Firstly, let’s see how physical replication (built into PostgreSQL since […]

On pglogical performance

January 8, 2016/1 Comment/in pglogical, PostgreSQL, Tomas' PlanetPostgreSQL /by Tomas Vondra

A few days ago we released pglogical, a fully open-source logical replication solution for PostgreSQL, that’ll hopefully get included into the PostgreSQL tree in a not-too-distant future. I’m not going to discuss about all the things enabled by logical replication – the pglogical release announcement presents a quite good overview, and Simon also briefly explained […]

Performance of Sequences and Serials in Postgres-XL

January 7, 2016/7 Comments/in 2ndQuadrant, Pavan's PlanetPostgreSQL, PostgreSQL /by Pavan Deolasee

In Postgres-XL, sequences are maintained at the Global Transaction Manager (GTM) to ensure that they are assigned non-conflicting values when they are incremented from multiple nodes. This adds significant overhead for a query doing thousands of INSERTs in a table with a serial column, incrementing sequence one at a time and making a network roundtrip […]

Index Overhead on a Growing Table

October 10, 2014/0 Comments/in Mark's PlanetPostgreSQL /by Mark Wong

This another simple test in continuation from last time. We will start with the same lineitem table as in the previous example. We will measure the time it takes to load the same 7.2GB text file repeatedly until the table size grows to about 1TB. We create a baseline with a table that has no indexes built on […]

Loading Tables and Creating B-tree and Block Range Indexes

October 3, 2014/2 Comments/in Mark's PlanetPostgreSQL /by Mark Wong

I have been looking at the new Block Range Indexes (BRIN) being developed for PostgreSQL 9.5. BRIN indexes are designed to provide similar benefits to partitioning, especially for large tables, just without the need to declare partitions. That sounds pretty good but let’s look in greater detail to see if it lives up to the hype. How large? Here’s […]

2ndQuadrant is now part of EDB