PostgreSQL Performance and Logical Replication in practice

Pivotal is hosting a PostgreSQL Meetup in Berlin.

There will be pizza and non-alcoholic drinks. Please let us know if you have special dietary needs. To find the EMC office, you head towards "Borsighallen" shopping center, the office is on the side street from the center. You can park your car in the center. If you come by public transport, the next subway stop is "Borsigwerke".

Our speakers:

Andres Freund will talk about PostgreSQL Performance and I/O.

How does Postgres perform IO, how can postgres be tuned for various IO
intensive workloads, and where does it need to be improved?
Many more intensive users of postgres have wondered how to tune shared_buffers, bgwriter_*, checkpoint_segments and some other parameters. There'll be some discussion about what these actually do, and which paraemeters are important for which workload. Additionally there's some IO workloads which postgres doesn't currently fare too well - we'll discuss why that is, and how some of these problems can be
addressed.

Oleksandr Shulgin, a database engineer from Zalando, will deliver a talk "Streaming huge databases using logical decoding".

In the talk he will describe Zalando's open-source data collection prototype that uses PostgreSQL's logical replication streaming capabilities to collect data from the database and stream it for later processing (Data Lake, Operational Data Store, automatic process monitoring, KPI calculation systems). The process includes taking a consistent snapshot of the database in a distributed and efficient manner and streaming the subsequent changes via a logical replication slot. This approach can be applied to online PostgreSQL major version upgrades, to fill event queues, for partial replication, etc. Use of Python makes it easy to support different target systems and to prototype rapidly.