Event schedule

Registrazione partecipanti

Coffee break

'

Pranzo

'

Lightning talk

Al desk ITPUG troverai una lavagna dove poter scrivere il tuo Nome ed il Titolo del tuo Lightning Talk. Non esitare!

Saluti e ringraziamenti - Marco Nenciarini, Presidente ITPUG

Lightning talk #1 - Guido Brugnara

Lightning talk #2 - Mladen Marinovic

Lightning talk #3 - Andrea Adami

Recruiting session

Keynote

Why Logical Replication?

In this talk we discuss the state of the art of Logical Replication for PostgreSQL. While we begin by comparing it with Physical Replication, the core part of this presentation is to examine a few specific use cases, including selective replication and no-downtime software upgrades. Throughout the talk we will also comment on pitfalls and limitations, as they arise in the use cases.

Partizionamento dichiarativo dei dati con PostgreSQL

Il partizionamento orizzontale è una delle tecniche di modellazione di un database di maggior successo per la scalabilità verticale di un database PostgreSQL. Dopo un excursus storico sul workaround disponibile già da PostgreSQL 8.1 e basato sull'ereditarietà, andiamo nel dettaglio del partizionamento dichiarativo introdotto in PostgreSQL 10, con un'occhiata sui lavori previsti per PostgreSQL 11.

PostgreSQL Tips & Tricks

PostgreSQL, oltre ad essere un database completo ed affidabile, riserva molte sorprese e funzionalità 'nascoste' che andremo ad scoprire in questo talk. In particolare esploreremo: • alcuni tipi di dato 'non convenzionali' • query stravaganti • psql per elefanti coraggiosi • indici preziosi • a caccia di estensioni uniche Incuriosito? Non mancare a questo talk, rimarrai sorpreso di ciò che il nostro Elefante può fare!

Replication becomes logical - How MultiMaster Replication developments work towards full integration to core PostgreSQL

Simon will use the example of Bi-Directional-Replication, Multi-master replication of geographically distributed databases in PostgreSQL, to explain how the development of PostgreSQL features for paying customers can be leveraged to improve the overall project. Postgres-BDR can be installed on bare metal, virtualized environments, or deployed in the cloud - it works as an extension to open source PostgreSQL versions 9.6+. The future features of BDR will reduce read and write latency for databases hosted far apart from each other, while remaining highly available with autofailover. Multi-master functionality from BDR 3.0 will be submitted as core patches to PG12 in 2019, furthering the progression towards getting it full function multi-master into core for Production use. Explanations of multiple enhancements of PostgreSQL, which were accomplished as one of the results of the development of Postgres-BDR, will be included.

Utilizzare Postgresql per analizzare stream di Kafka

Apache Kafka è una piattaforma di raccolta e l'elaborazione di messaggi in real time. Viene utilizzato in un numero sempre maggiore di contesti per gestire flussi di eventi quali supervisioni, transazioni e altre attività in real time. Questo intervento si concentra sulla connessione tra Kafka e PostgreSQL per aggiornare automaticamente un database relazionale con eventi provenienti da Kafka, consentendo di utilizzare le funzionalità di reporting e aggregazione di dati di PostgreSQL sul flusso di dati in real time.

Replica logica in PostgreSQL: il futuro è adesso

A partire dalla versione 10, la replica logica entra nel core di PostgreSQL, permettendo di replicare dati in maniera efficiente fra nodi diversi. In questo talk vedremo come funziona questo metodo alternativo alla replica fisica, quanto sia efficiente rispetto ad altri metodi di replica e come, con qualche accorgimento, sia possibile avere lo stream delle modifiche accessibile da Python. Naturalmente daremo anche uno squardo al futuro, parlando dei miglioramenti che saranno inclusi in PostgreSQL 11.

PostgreSQL High Availability using repmgr and pgbouncer

In the company I work for we have implemented PostgreSQL High Availability using repmgr and pgbouncer. We have additionally prepared some custom scripts to avoid split brain situations. We are using puppet (foreman) for installing and configuring PostgreSQL, the same is used for configuring High Availability (with few manual steps). I would like to give a presentation about the setup we're doing for this High Availability solution.

Fun (and profit) with ZFS and Postgres

ZFS is a filesystem, originally developed for Solaris, that finally brings advanced filesystem features (compression, snapshots, and checksums, among others) to Linux. I selected the ZFS-on-Linux port as the key component of an internal tool created with the purpose of better supporting the team in all those scenarios where a replica of the production Postgres database might be required: testing query optimizations, database migrations, etc. While it was a lot of fun for me to work on it, the tool proved, most importantly, to be extremely useful to the whole team. The presentation dives into the technical details of the tool, introduces ZFS key features, why one would want to use it, and then explores some other interesting ZFS use cases

Greenplum storage management

Greenplum differs from Posgres in many ways, one of this is storage management, which includes data redundancy needs introduced by shared-nothing paradigm, external tables and polymorfic storage. This session explain how these features are implemented and how to use them

Greenplum Database: Evolving advances analytics on postgres

Greenplum brings massively parallel processing to the world of postgresql to enable analysis of Petabyte scale data using a standard PostgreSQL interface. This talk will explain how Greenplum enables massively parallel proecssing and how the future roadmap and integration with Kubernees will enable Greenplum to scale to new heights.

How postgis changed the insurance market in Brazil

We can offer a one-size-fits-all product, or we can truly understand our users and offer something valuable and customized to their needs. Geolocation is the key to learn what is going on around them to make better, user-centric decisions.

A New Way to avoid trigger based logging in PostgreSQL

Logging events in databases has been around for ages and we have been more than used to the traditional way of doing so using triggers. In this talk, I'd be glad to show how database logging trascends beyond using triggers and turn to the not so new Logical decoding in PostgreSQL. Thanks to Logical Decoding, log tables can now me moved to a different database servers where cheap hardware could be deployed for not so critical log tables. Beyond just logging , Logical Decoding also allows for all other exciting usage like Data warhousing ETL processes , data pipelines, queuing and the rest.

Living in a connected world: data exchange features belonging to Greenplum

Pivotal Greenplum includes many features to exchange data between external data sources and the GPDB database: database links, PXF, external tables, Pivotal Gemfire connector, Spark connector .... many ways to connect Greenplum with the external world in a easy and effective way.

Pump up your elephants with Patroni

Patroni is a high availability solution to manage hundreds of databases in the cloud, as well as in traditional data centers. It implements automatic failover and works together with Etcd, Zookeeper, Consul or Kubernetes API to store and retrieve PostgreSQL cluster information in a consistent way ensuring that there is only one leader at a time. Unlike the majority of existing solutions for automatic failover, it requires a minimal effort to configure the HA cluster and supports autodiscovery of new nodes. In this talk, I will describe how Patroni works, present a live-demo of creating a new high-availability cluster and share experiences of running a few hundreds PostgreSQL HA clusters in Zalando’s Database-as-a-Service infrastructure on EC2 instances and on Kubernetes. Patroni is developed by Zalando in cooperation with other contributors on GitHub: https://github.com/zalando/patroni

Subito Vs GDPR

Quando pensi che la luce infondo al tunnel sia l'uscita... Un'opportunità per migliorare il nostro prodotto.

Visualizza i tuoi dati con Superset

Per avere i nostri dati al sicuro li abbiamo scritti in un database PostgreSQL. Ma per analizzarli? Superset! Superset è una piattaforma open source che permette di creare visualizzazioni dinamiche di dati senza scrivere una riga di codice. Vedremo quali sono le caratteristiche e le funzionalità di Superset e come possiamo usarlo per esplorare e visualizzare i dati di un database.

Machine Learning with PostGreSQL

Amazon, Google, Facebook, IBM e molti altri propongono sistemi e librerie per il Machine Learning. E PostgreSQL cosa può fare? Nel talk si evidenzieranno e studieranno alcuni esempi di utilizzo della libreria MADLib e strumenti per l'analisi del linguaggio naturale.

PostgreSQL Database-as-a-Service with Kubernetes

Kubernetes is emerging as a standard open-source platform to quickly roll out containerised applications, automatically manage resources and provide universal abstractions for the hardware/cloud layer, but can we take advantage of it for deploying and running PostgreSQL databases? The answer is yes, and we at Zalando have developed open-source tools to help you with that task. In this talk I will explain how we embraced Kubernetes at Zalando to run our staging and production databases, avoiding commercial solutions lock-in and saving costs. I will describe the benefits and pitfalls of running production databases on Kubernetes and, finally, show open-source tools we have built for application developers to deploy and manage PostgreSQL clusters by writing short manifests describing a few essential properties of the result.

DDL Locks

Query hacking: Making queries behave like you want to

Did you ever had a query that runs fine on the development servers, but runs very slow on production. And by slow I mean 4 hours slower than the expected hundreds of milliseconds. After digging a bit you find out it is using a suboptimal plan, which is the cause of the slow execution. How to fix that? This talk will cover several ways of influencing the planner decisions with different options, query rewriting with CTEs, OFFSET 0 and clever tricks that leverage the query planer heuristics. Every method has its drawbacks so we will point out the problematic parts when applicable.

Autovacuum: Friend or enemy?

Many PostgreSQL instances have autovacuum turned off because of performance issues. The results of this choice can vastly vary between ok and catastrophic. However, is autovacuum your friend or enemy? To answer that you have to know how PostgreSQL works, what is table/index bloat and what is the problem with transaction visibility information (XID) wraparound. In this talk we will show what can happen if you turn it off, and how can we tweak the autovacuum parameters to get the most from it. We will also cover existing tools and present an internal tool that we plan to open source.

Data migrations

La versione di PostgreSQL è solitamente supportata per 5 anni dalla Community. Ciò significa che, se hai un progetto serio su PostgreSQL, probabilmente dovrai migrare i tuoi dati a una versione più recente per ottenere le normali correzioni di sicurezza e correzioni di errori. Le versioni più recenti solitamente offrono ulteriori vantaggi: prestazioni migliori sullo stesso hardware, nuove funzionalità ed estensioni. Ma come migrare i tuoi dati? pg_dump / pg_restore è la prima cosa che le persone usano se possono, e funzionano alla grande. Sfortunatamente, l'applicazione nel fra tempo deve essere offline. Se il database ha una dimensione di rilievo, sarà offline un periodo di tempo inaccettabile. Alla ricerca di soluzioni a questo problema, possiamo trovare diversi strumenti che possono aiutarci: • pg_upgrade • Slony-I • pglogical (con pgrepup) In questa presentazione, mostreremo i risultati del test di alcune di queste soluzioni sul nostro database di produzione (900 + GB). Inoltre, abbiamo testato la migrazione dei nostri dati con il comando COPY.

Benvenuti