BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Pentabarf//Schedule 0.3//EN CALSCALE:GREGORIAN METHOD:PUBLISH X-WR-CALDESC;VALUE=TEXT:PostgreSQL devroom X-WR-CALNAME;VALUE=TEXT:PostgreSQL devroom X-WR-TIMEZONE;VALUE=TEXT:Europe/Brussels BEGIN:VEVENT METHOD:PUBLISH UID:10743@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T100000 DTEND:20200202T105000 SUMMARY:Fibonacci Spirals and 21 Ways to Contribute to Postgres—Beyond Code DESCRIPTION:
Postgres is growing like gangbusters: in popularity, in adoption, and in the size of the ecosystem. And over 400 developers contribute code to Postgres today: their expertise, design chops, and skill are big factors in the increasing popularity of Postgres. But what if you’re not a developer? Are there things you can do to help grow the usage and popularity of Postgres? And are these non-code ways to contribute to Postgres important? Valued? Will they make a real difference?
If you love Postgres and want to help drive Fibonacci growth of the Postgres community, this talk is for you. I’ll walk through 21 different (and important) ways to contribute to Postgres—along with tips and resources for getting started.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2020/schedule/2020/schedule/event/postgresql_fibonacci_spirals_and_21_ways_to_contribute_to_postgres_beyond_code/ LOCATION:H.2214 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Claire Giordano":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10744@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T110000 DTEND:20200202T115000 SUMMARY:Find your slow queries, and fix them! DESCRIPTION:Where, oh where, is all that time going? What in the world is that database thing doing?! This talk will help you understand what's happening (and why) and how to analyze poor query performance. We'll also go over steps and strategies to take to improve them and get the performance (and scalability!) you need.
It all starts with figuring out what queries are slow, we'll do that by going into the various PostgreSQL configuration options for logging queries and a few helpful modules for getting even more information about ongoing queries. Next we'll go over EXPLAIN and EXPLAIN ANALYZE output for select queries, what the EXPLAIN output means in terms of how the query is being executed. Lastly (this is the good part- you have to stay til the end to get it!) we'll go over ways to improve the queries, including index creation, rewriting the query to allow PG to use a different plan, and how to tune parameters for specific queries.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2020/schedule/2020/schedule/event/postgresql_find_your_slow_queries_and_fix_them/ LOCATION:H.2214 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Stephen Frost":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10745@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T120000 DTEND:20200202T125000 SUMMARY:A Deep Dive into PostgreSQL Indexing DESCRIPTION:Indexes are a basic feature of relational databases, and PostgreSQL offers a rich collection of options to developers and designers. To take advantage of these fully, users need to understand the basic concept of indexes, to be able to compare the different index types and how they apply to different application scenarios. Only then can you make an informed decision about your database index strategy and design. One thing is for sure: not all indexes are appropriate for all circumstances, and using a ‘wrong’ index can have the opposite effect that you intend and problems might only surface once in production. Armed with more advanced knowledge, you can avoid this worst-case scenario! We’ll take a look at how to use pgstatstatment to find opportunities for adding indexes to your database. We’ll take a look at when to add an index, and when adding an index is unlikely to result in a good solution. So should you add an index to every column? Come and discover why this strategy is rarely recommended as we take a deep dive into PostgreSQL indexing.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2020/schedule/2020/schedule/event/postgresql_a_deep_dive_into_postgresql_indexing/ LOCATION:H.2214 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Ibrar Ahmed":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10746@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T130000 DTEND:20200202T135000 SUMMARY:PostgreSQL on K8S at Zalando: Two years in production DESCRIPTION:Many DBAs avoid any kind of cloud offering and prefer to run their databases on dedicated hardware. At the same time companies demand to run Postgres at scale, efficiently, automated and well integrated into the infrastructure landscape. The arrival of Kubernetes provided good building blocks and an API to interact with and with it solve many problems at the infrastructure level.
The database team at Zalando started running highly-available PostgreSQL clusters on Kubernetes more than two years ago. In this talk I am going to share how we automate all routine operations, providing developers with easy-to-use tools to create, manage and monitor their databases, avoiding commercial solutions lock-in and saving costs, show open-source tools we have built to deploy and manage PostgreSQL cluster on Kubernetes by writing short manifests describing a few essential properties of the result.
Operating a few hundred PostgreSQL clusters in a containerized environment has also generated observations and learnings which we want to share: infrastructure problems (AWS), how engineers use our Postgres setup and what happens when the load becomes critical.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2020/schedule/2020/schedule/event/postgresql_postgresql_on_k8s_at_zalando_two_years_in_production/ LOCATION:H.2214 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Alexander Kukushkin":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10747@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T140000 DTEND:20200202T145000 SUMMARY:An ultimate guide to upgrading your PostgreSQL installation DESCRIPTION:Even an experienced PostgreSQL DBA can not always say that upgrading between major versions of Postgres is an easy task, especially if there are some special requirements, such as downtime limitations or if something goes wrong. For less experienced DBAs anything more complex than dump/restore can be frustrating.
In this talk I will describe why we need a special procedure to upgrade between major versions, how that can be achieved and what sort of problems can occur. I will review all possible ways to upgrade your cluster from classical pg_upgrade to old-school slony or modern methods like logical replication. For all approaches, I will give a brief explanation how it works (limited by the scope of this talk of course), examples how to perform upgrade and some advice on potentially problematic steps. Besides I will touch upon such topics as integration of upgrade tools and procedures with other software — connection brokers, operating system package managers, automation tools, etc. This talk would not be complete if I do not cover cases when something goes wrong and how to deal with such cases.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2020/schedule/2020/schedule/event/postgresql_an_ultimate_guide_to_upgrading_your_postgresql_installation/ LOCATION:H.2214 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Ilya Kosmodemiansky":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10748@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T150000 DTEND:20200202T155000 SUMMARY:The State of (Full) Text Search in PostgreSQL 12 DESCRIPTION:How to navigate the rich but confusing field of (Full) Text Search in PostgreSQL. A short introduction will explain the concepts involved, followed by a discussion of functions, operators, indexes and collation support in Postgres in relevance to searching for text. Examples of usage will be provided, along with some stats demonstrating the differences.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2020/schedule/2020/schedule/event/postgresql_the_state_of_full_text_search_in_postgresql_12/ LOCATION:H.2214 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Jimmy Angelakos":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:10749@FOSDEM20@fosdem.org TZID:Europe-Brussels DTSTART:20200202T160000 DTEND:20200202T165000 SUMMARY:RTFM DESCRIPTION:Reading the manual before starting a new work is always a good practice.
However some situations like pressure for delivery or lack of attention may lead to wrong assumptions that cause unpredictable results or even disasters.
The talk, in a semi serious way, will walk the audience through some of corner cases caused by the lack of the good practice of RTFM.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2020/schedule/2020/schedule/event/postgresql_rtfm/ LOCATION:H.2214 ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Federico Campoli":invalid:nomail END:VEVENT END:VCALENDAR