development Archives - 2ndQuadrant

Posts

Developing on many versions of PostgreSQL at once

August 19, 2019/0 Comments/in Craig's PlanetPostgreSQL /by craig.ringer

In a developer’s ideal world there’s only one stable and one development version of the product. Everyone updates immediately to the next stable version and nobody cares about anything older. As far as I can tell this has never actually happened, ever, in the history of anything. Working on many versions PostgreSQL is a mature […]

I am Developer! (And You Can Too!)

April 5, 2019/0 Comments/in Shaun's PlanetPostgreSQL /by Shaun Thomas

A while back, 2ndQuadrant notified a few of us that we should get more involved in Postgres Development in some capacity. Being as I’ve essentially fallen off the map in corresponding with the mailing lists in general, it would be a good way to get back into the habit. But wait! Don’t we want more […]

PostgreSQL 10 Roadmap

August 2, 2016/8 Comments/in 2ndQuadrant, Simon's PlanetPostgreSQL /by Simon Riggs

At the PostgreSQL developer meeting we discussed putting up everybody’s roadmap projects in one place: http://wiki.postgresql.org/wiki/PostgreSQL10_Roadmap.

Visual PostgreSQL debugging

May 3, 2016/2 Comments/in Craig's PlanetPostgreSQL /by craig.ringer

Having recently been doing some debugging work where many watchpoints, conditional breakpoints etc were necessary I’d like to shout out to a really useful tool: The standalone CDT debugger. It’s part of the Eclipse project, but before you run screaming – it doesn’t require project setup or anything and it serves as a good GUI […]

Column Store Plans

April 25, 2016/5 Comments/in 2ndQuadrant, Alvaro's PlanetPostgreSQL, PostgreSQL /by Álvaro Herrera

Over at pgsql-general, Bráulio Bhavamitra asks: I wonder if there is any plans to move postgresql entirely to a columnar store (or at least make it an option), maybe for version 10? This is a pretty interesting question. Completely replacing the current row-based store wouldn’t be a good idea: it has served us extremely well […]

Managing a PostgreSQL Commitfest

February 18, 2016/1 Comment/in Alvaro's PlanetPostgreSQL, PostgreSQL /by Álvaro Herrera

If you’ve been following PostgreSQL development for the last few years, you’ve probably heard the term commitfest manager a few times. You probably already know what a commitfest is, but why is there a manager? Since I spent a good deal of time this past January managing one, I’ll explain. At its heart, a PostgreSQL […]

Compiling and debugging PostgreSQL’s PgJDBC under Eclipse

September 24, 2014/2 Comments/in Craig's PlanetPostgreSQL /by craig.ringer

I’ve always worked on PgJDBC, the JDBC Type 4 driver for PostgreSQL, with just a terminal, ant and vim. I recently had occasion to do some PgJDBC debugging work on Windows specifics so I set up Eclipse to avoid having to work on the Windows command prompt. As the process isn’t completely obvious, here’s how […]

Compiling PostgreSQL extensions with Visual Studio on Windows

January 11, 2014/47 Comments/in Craig's PlanetPostgreSQL /by craig.ringer

I’ve seen a number of users struggling with building PostgreSQL extensions under Visual Studio, so I thought I’d see what’s involved in getting it working. The result is this tutorial, showing how to compile a simple extension with Visual Studio 2010 Express Edition. Requirements You will need a supported version of Visual Studio installed. These […]

Postgres and devops: testing 9.3 with Vagrant and Puppet – part two

November 4, 2013/2 Comments/in Gabriele's PlanetPostgreSQL /by Gabriele Bartolini

In a previous blog post, I have gone through the steps of setting up a basic CentOS 6.4 64bit Linux distribution using Vagrant on your Ubuntu 12.04 LTS Linux. We will continue digging in the devops culture/movement and finally setup PostgreSQL 9.3 using Puppet in a local virtual machine.

Testing new PostgreSQL versions without messing up your existing install

August 30, 2013/8 Comments/in Craig's PlanetPostgreSQL /by craig.ringer

People are often hesitant to test out a new PostgreSQL release because they’re concerned it’ll break their current working installation. This is a perfectly valid concern, but it’s easily resolved with a few simple protective measures: Build PostgreSQL from source as an unprivileged user Install your PostgreSQL build within that user’s home directory Run PostgreSQL […]