The traditional Monash University Prato Centre, historical venue of the first European PGDay, will host the first edition of another conference: Open Source Software for Business, aka OSS4B. OSS4B 2013 will take place in Prato, Tuscany, Italy on September 19 and 20. Through the experience gained with several organisations of PostgreSQL related events, we have […]
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 […]
(This article is written with reference to PostgreSQL 9.3. If you’re using a newer version please check to make sure any limitations described remain in place.) PostgreSQL offers several tools for searching and pattern matching text. The challenge is choosing which to use for a job. There’s: LIKE and ILIKE SQL pattern matching; ~ and […]
En noviembre del 2012 asistí al PgDay en Buenos Aires. Ahí presente la charla “Autovacuum, ¿bendición o maldición? Afrontando el reto”. En uno de los puntos de la charla explique, o al menos eso trate, que es necesario tratar de prevenir que el autovacuum ejecute VACUUM FREEZE. El problema con VACUUM FREEZE ejecutado por el […]
One of the most recurring questions I get from users that are starting their long and prosperous journey with PostgreSQL involves connecting with the “postgres” user.
Version 1.2.1 of Barman, Backup and Recovery Manager for PostgreSQL, has been released, introducing bandwidth limitation for both backup and recovery operations at three different levels: global, server (PostgreSQL instance) and tablespace.
In our previous article we went through describing what retention policies are and how they can be enforced on your PostgreSQL server backups with Barman 1.2. In this post, we will go through the configuration aspects.
Defining a disaster recovery plan involves defining backup policies. A key aspect of backup policies is to define how long backup data is retained for disaster recovery purposes. This applies to all digital content, including PostgreSQL databases. Barman 1.2.0 introduces automated management of backup retention policies of PostgreSQL servers.
The first Australian PostgreSQL conference has come to an end and I am extremely happy that I was part of it. The event took place in Melbourne, at the offices of Experian Hitwise in St Kilda Rd. I must confess that, going back to the same building where I had worked in 2005/2006, was a […]
As interest in PostgreSQL grows, so does the rate at which new patches are proposed. To maintain the high level of quality in PostgreSQL it is important that all patches be checked and reviewed, so that what gets added to the codebase is good quality. Some of this evaluation requires a lot of expertise in […]