About The Event

PostgresLondon is the perfect opportunity for PostgreSQL users, developers, and anyone with a keen interest in the most advanced open source database for enterprises to get together and learn, share ideas, and network in one of the most international cities in the world. This 2-day event highlights the latest developments for PostgreSQL, including new features added to in the latest version, current projects under development, and the future direction of PostgreSQL – including an insider’s look at what’s to come in upcoming major releases. PostgreSQL adoption is growing exponentially every year, and PostgresLondon is a place where enterprise users come together to share their success stories.

There is also a full day of hands-on training offered on 1 July, the day before the general conference.


London, United Kingdom


Tuesday to Wednesday
July 2 to 3, 2019


30 Euston Square
Kings Cross, London

30 Euston Square is a building located at the corner of Euston Road and Melton Street, London NW1.


Our Sponsors




Travelodge London Euston – Approx 5 mins from Venue and approx. £150 per night.

TheWesley – Approx. 5 mins from venue and approx. £150 per night.

Hilton – London Euston – Approx. 5 mins from venue – approx. £180 per night.


  • Day 1

    July 2, 2019

  • PostgreSQL 12 is not done yet. In fact, most people have not upgraded to 11 yet! But most of the things that will be in the next version, targeted for release later in 2019, are already done. This talk will outline some of the bigger and more interesting features to look forward to!

  • One of the new features in PostgreSQL 10 is the ability to create multi-column statistics, helping the optimizer understand dependencies between columns. This talk will explain a bunch of important questions - why we need this capability at all, how it works, which cases it can address currently, and which improvements are in the queue for PostgreSQL 12.

  • Have you ever encountered a transient performance issue, that was hard to investigate only from the database point of view? On top of how many layers of abstraction your database is working? What is the difference between running your database on a bare metal, VM or inside a container? PostgreSQL does not work in the vacuum, it heavily relies on functionality provided by an underlying platform. And sometimes to answer these questions above one needs to step back and look at a problem not only from a database point of view. In this talk we will discuss how to achieve that, how to tame such tools as strace, perf or eBPF to troubleshoot intricate issues and stay curious.

  • The SQL standard is not standing still. SQL:2016 introduced the latest round of features, and a new standard is expected in 2020. What does that mean for PostgreSQL, the most SQL-conforming relational database system? Let's take a look what new features recent SQL standard releases have brought. One of the main features of SQL:2016 is JSON support. PostgreSQL has been a leader of JSON support among relational databases, and PostgreSQL 12 and beyond will bring the SQL standard interfaces on top of existing JSON support. Other features in SQL:2016 being considered for future PostgreSQL releases include row-pattern recognition and several new functions and data types. A number of new features are being worked on for SQL:2020, among which graph database functionality is the most notable. We'll discuss some of these past and future features, the relationship with other SQL implementations, the SQL standardization process and adoption in PostgreSQL.

  • You're woken up in the middle of the night to your phone. Your app is down and you're on call to fix it. Eventually you track it down to ""something with the db,"" but what exactly is wrong? And of course, you're sure that nothing changed recently. Knowing what to fix, and even where to start looking, is a skill that takes a long time to develop. Especially since Postgres normally works very well for months at a time, not letting you get practice! In this talk, I'll share not only the more common failure cases and how to fix them, but also a general approach to efficiently figuring out what's wrong in the first place.

  • We've been trying to scale PostgreSQL since forever. What ways have people come up with? How do they work? Where is that now? Will review all known architectures, comment on ones that are no longer available and review ones that are still around and in use. Comments on scalability of various workloads, query consistency, ACID, BASE and other topics.

  • Day 2

    July 3, 2019

  • Postgres has the unique ability to act as a powerful data aggregator in many data centers. This talk shows how Postgres's extensibility, access to foreign data sources, and ability handle NoSQL-like and data warehousing workloads gives it unmatched capabilities to function in this role. Slides at https://momjian.us/main/writings/pgsql/central.pdf

  • Really often, what we, developers, do something that would drive DBAs crazy: we trust our ORM to handle the creation of indexes. That's so easy ! Why not use it right? So what's the problem then ? Well most ORMs only use BTree indexes. Often, it's what we need. But why cut ourselves from all the other index types ? This talk covers PostgreSQL indexes types (B-Tree, GIN, GiST, SP-GiST, BRIN and Hash). We will take a look into how each type is implemented in Postgres source code and why it makes it more fit to certain data types. Through the very real example of an application to organise crocodiles dentist's appointments, examples of use-cases for each index type will be explained to understand how to choose the right type. At the end of the talk, you should be familiar with the internal data structure of indexes, which could help you choose the best index for you data type and query operators !

  • Window functions are a very useful tool; since their introduction 10 years ago, they have been gradually adopted for various use cases where a simple aggregation is not flexible enough: incremental totals, moving averages, etc. The latest options introduced in PostgreSQL 11 complete the implementation according to the SQL:2011 standard, adding capabilities such as range frames, GROUPS mode and exclusions. In this talk we will review what users can do with window functions nowadays, and illustrate each specific feature with an example which is examined in detail.

  • PostgreSQL's WAL is one of the core points of PostgreSQL, and used in many areas: Backup, replication, etc. In this talk, I will mention about everything about WAL that a PostgreSQL DBA must know: - What is WAL? - What does it include? - How to read it? - What about wal_level ? - Replication and WAL - Backup and WAL - PITR and WAL - Other topics

  • Coming to PostgreSQL after years of Oracle performance tuning, I realize that I approach PostgreSQL with tools and methods than are different from what a 'native' postgres DBA will start with. What made my job easier on Oracle is also available, and free, for PostgreSQL: - PGIO is more appropriate than pgbench when analyzing the platform performance - pgSentinel, with its ASH sampling approach, is more powerful than statistics and ratios - measuring work done, from linux system calls, rather than response time, to ensure predictable and scalable performance Let's make them better known with some demos.

  • Celeen and Micah are both experienced developers, but had never managed large databases. Then they joined Braintree's Database team, which is responsible for the maintenance, scaling, and application interactions of twenty high availability Postgres clusters storing a hundred terabytes that drive the processing of more than 6 billion payments a year. In this talk, we discuss learning about the inner workings of Postgres, how Braintree works with Postgres' strengths, design and community to help overcome stresses at scale, and the perspective gained moving from an application development team to a database team.