Firefly2022-03-242022-03-241https://www.postgresql.eu/events/pgdayparis2022/schedule/08:3000:30Otherhttps://www.postgresql.eu/events/pgdayparis2022/schedule/session/3671/Breaks09:0000:10Auditoriumhttps://www.postgresql.eu/events/pgdayparis2022/schedule/session/3675/Open/Close09:1500:45AuditoriumIt's not uncommon to deploy a microservice-based, containerized application on Kubernetes in a public cloud these days. In many cases, applications require a PostgreSQL database deployment as well. There are two often considered alternatives: * Use DBaaS - for example Google CloudSQL for PostgreSQL * Deploy the database on Kubernetes with the application For your PostgreSQL deployment, you're most likely looking for: ease of use ("day 1" and "day 2" operations), reliability (high availability, RPO, RTO), and cost-efficiency (who likes to pay a lot?) We'll explore both deployment solutions and compare them from different angles to make the differences and capabilities clear. You'll be better equipped to decide how to run PostgreSQL for your cloud-native application. For example, we'll focus on Google CloudSQL and Percona Distribution for PostgreSQL Operator on Google Kubernetes Engine (GKE). Still, most of the knowledge is universal across cloud platforms and DBaaS solutions.https://www.postgresql.eu/events/pgdayparis2022/schedule/session/3612/TalksMichał Nosek10:0000:20Otherhttps://www.postgresql.eu/events/pgdayparis2022/schedule/session/3672/Breaks10:2000:45AuditoriumMost organizations or database teams don't have the luxury of looking after just a single database application. Some will manage at least a few applications, others will have hundreds. In most organizations, the question of multi-tenancy will therefore probably arise. The Postgres environment can be designed in various different ways to accommodate multiple customers and/or applications. For example: - each application could have its own Postgres cluster - we could create a separate database per application within a shared cluster - we could create a single database that contains a separate schema per application - we may allow multiple customers to share a single schema, with the (shared) tables partitioned by customer But which of these is the “right” option? The answer is, as always, “it depends”. The correct method is the one that provides the required balance between performance, security, high availability and manageability. In this presentation, we'll look at the different multi-tenant architectures and the advantages and disadvantages of each. It should enable you to design the most appropriate database environment for your applications.https://www.postgresql.eu/events/pgdayparis2022/schedule/session/3475/TalksKaren (Karrie) Jex11:1000:45AuditoriumHaving used mostly proprietary RDBMS for a long time, Société Générale decided to switch to PostgreSQL as its go-to database in 2017 to accelerate its digital transformation. We are happy to share that PostgreSQL is now our most used database. We will share some history of this transition, some of the tools we used, some technical and not so technical challenges we faced. The goal is to share some of the lessons we learned along the way so that if your organization chooses to switch to PostgreSQL, you will be better equipped to make this journey smoother.https://www.postgresql.eu/events/pgdayparis2022/schedule/session/3650/TalksAnthony Nowocien12:0000:30AuditoriumSince April 2021 and the 2.33 release, pgBackRest allows using multiple repositories at the same time. This brings a lot of benefits like, for example, redundancy and the ability to define various retention policies. In this short talk, we'll discover the impact of this new feature on the existing pgBackRest commands. We'll also see how powerful it is to combine this functionality with another great feature: asynchronous archiving.https://www.postgresql.eu/events/pgdayparis2022/schedule/session/3567/TalksStefan Fercot12:3001:30Otherhttps://www.postgresql.eu/events/pgdayparis2022/schedule/session/3673/Breaks14:0000:45AuditoriumAccepting a new professional challenge in April 2019, I left the retail ecosystem for the e-commerce platforms. I arrived at Mirakl and discovered a highly automated architecture. There has been no senior DBA for several months. I was expected to modernize the PostgreSQL databases. I share my experience and show what worked and what didn't!https://www.postgresql.eu/events/pgdayparis2022/schedule/session/3643/TalksThomas BOUSSEKEY14:5000:45AuditoriumPostgreSQL provides now a good set of features around table partitioning. We'll explore what is already included, the benefits and the limitations. And the next steps. Finally, we'll look at scale: how we extend PostgreSQL with foreign data servers. And eventually how this is related to «horizontal partitioning» at the server level.https://www.postgresql.eu/events/pgdayparis2022/schedule/session/3546/TalksCédric Villemain15:3500:20Otherhttps://www.postgresql.eu/events/pgdayparis2022/schedule/session/3674/Breaks15:5500:45AuditoriumPostgreSQL 15 is slowly approaching feature freeze state, and at this point we have at least some ideas of what features will be included. This talk will take a quick look at what's in there already, and what's in the queue!https://www.postgresql.eu/events/pgdayparis2022/schedule/session/3628/TalksMagnus Hagander16:4500:45AuditoriumThis presentation explains how open source software can live for a very long time, and covers the differences between proprietary and open source software life cycles. It also covers the increased adoption of open source, and many of the ways that Postgres is innovating to continue to be relevant.https://www.postgresql.eu/events/pgdayparis2022/schedule/session/3506/TalksBruce Momjian17:3500:15Auditoriumhttps://www.postgresql.eu/events/pgdayparis2022/schedule/session/3676/Open/Close