Henrietta Dombrovskaya

PostgreSQL does not have any prescribed guidelines for the use of schemas, also called namespaces. A namespace is just one of many attributes of an object, whether an object is a table, a view, a function, or any other object type available in PostgreSQL.

The goal of this community event is to help organizers, speakers, and others learn to grow the community around them. We will discuss growing speakers, reaching out to other groups, gathering sponsors, and organizing events.

We kick off with a short DEV/DBA/DBRE panel discussion to surface the most common “Postgres at scale” failures. Then the mic is open: attendees can step up for a lightning confession : A real production “obvious fix” that backfired, the metric that proved it, and what they’d do differently.

This training is based on PostgreSQL Query Optimization book Dombrovskaya, Novikov, Bailliekova) and uses postgres_air database for real-life examples of queries.

An open discussion with Postgres community members around the topic of scaling up for challenging workloads. We will be looking at how PostgreSQL deals with each of these challenges, and discussing possible mitigations, tuning tips or workarounds.

Big events, like PGConf EU, allow participants to interact with a large group of top professionals from all over the world and choose from a variety of presentations. However, not everybody can afford long-distance travel and several days off work.

It’s a well-known fact, that although the database performance is great, and each query is executed in milliseconds, the overall application response time may be slow, making the users wait for a response for extended periods of time.

It's a well-known fact, that although the database performance is great, and each query is executed in milliseconds, the overall application response time maybe slow, making the users wait for response for an extended periods of time.

Everything shall pass except Object-Relational Impedance Mismatch. Despite many years of research and development in this area, applications and databases still struggle with communication issues.

At Braviant Holdings we consider foreign data wrappers to be the best thing even introduced in PostgreSQL. We use them virtually everywhere, both for our apps which interact with OLTP databases and for the ETL for our Data Warehouse.