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:15010@FOSDEM23@fosdem.org TZID:Europe-Brussels DTSTART:20230205T090000 DTEND:20230205T095000 SUMMARY:Tour de Data Types: VARCHAR2 or CHAR(255)? DESCRIPTION:
Ever wondered what might be the best data type for a certain use case? Is it better to use INTEGER or BIGINT, and should you use TIMESTAMP or is it better to use TIMESTAMPTZ? When is the last time you migrated a legacy database and wondered what to use as replacement for VARCHAR2 or CHAR(255)? How to store IP addresses or geographical data, does that fit into VARCHAR or is there something more suitable?
PostgreSQL 15 comes with around 40 different data types preinstalled. This talk looks beyond INTEGER and VARCHAR and dives into some of the lesser known PostgreSQL data types. Use cases and examples show which data type is a good fit for a certain situation.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2023/schedule/2023/schedule/event/postgresql_tour_de_data_types_varchar2_or_char_255/ LOCATION:UA2.118 (Henriot) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Andreas Scherbaum (ads)":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:14967@FOSDEM23@fosdem.org TZID:Europe-Brussels DTSTART:20230205T100000 DTEND:20230205T105000 SUMMARY:How to Give Your Postgres Blog Posts an Outsize Impact DESCRIPTION:One of the sayings about development in the Postgres world is “it’s not just open source, it’s open engineering.” In the spirit of openness, this talk will show you how to increase the impact and the reach of your Postgres blog posts. These best practices begin with empathy for your readers—and cover lots of ground from there, including key things to know about SEO, as well as tips on how to promote your blog post. This talk is an updated version of the PGConf EU 2022 talk I gave in Berlin and it's not just theory: real-world examples are included throughout the talk.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2023/schedule/2023/schedule/event/postgresql_how_to_give_your_postgres_blog_posts_an_outsize_impact/ LOCATION:UA2.118 (Henriot) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Claire Giordano":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:14968@FOSDEM23@fosdem.org TZID:Europe-Brussels DTSTART:20230205T110000 DTEND:20230205T115000 SUMMARY:When it all GOes right DESCRIPTION:This talk covers how to use PostgreSQL together with the Golang (Go) programming language. I will describe what drivers and tools are available and which to use nowadays.
In this talk I will cover what design choices of Go can help you to build robust programs. But also, we will reveal some parts of the language and drivers that can cause obstacles and what routines to apply to avoid risks.
We will try to build the simplest cross-platform application in Go fully covered by tests and ready for CI/CD using GitHub Actions as an example.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2023/schedule/2023/schedule/event/postgresql_when_it_all_goes_right/ LOCATION:UA2.118 (Henriot) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Pavlo Golub":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:15094@FOSDEM23@fosdem.org TZID:Europe-Brussels DTSTART:20230205T120000 DTEND:20230205T125000 SUMMARY:AMENDMENT The Human Factor: Why Database teams Need Crew Resource Management DESCRIPTION:Our industry talks a great deal about human error, with the idea that we can automate away human mistakes. However, we are generally missing a fundamental and technical model of how we as humans operate, and what can be done to minimize errors and maximize good outcomes. As much as "human error" sometimes gets us into problems, the human factor is the only thing that gets us out.
Fortunately, as an industry, we do not have to figure this out all by ourselves. Medicine, rail operators, and most importantly, airlines have been on the forefront of research and training in this field.
In this presentation you will learn:- The history of Crew Resource Management- Specific case-based examples on how database teams suffer the same problems that flight crews, fire crews, and medical teams face- What crew resource management training teaches- How to Implement Crew Resource Management in your teams or company- How Crew Resource Management training delivers benefits
The speaker offers no commercial services in this field but has been involved in implementing crew resource management programs in database teams.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2023/schedule/2023/schedule/event/postgresql_the_human_factor_why_database_teams_need_crew_resource_management/ LOCATION:UA2.118 (Henriot) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Christopher Travers":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:14970@FOSDEM23@fosdem.org TZID:Europe-Brussels DTSTART:20230205T130000 DTEND:20230205T135000 SUMMARY:Bulk Inserts With PostgreSQL: Four Methods For Efficient Data Loading DESCRIPTION:In a world where data continues to grow at an overwhelming rate, knowing how to load and insert data into PostgreSQL as efficiently as possible is a key skill for any software or data engineer. Whether loading data from files, manually generating multi-valued INSERT or UPSERT statements, or using some of the more popular language SDKs, knowing which option is right for each situation can sometimes be difficult to figure out.
This talk will review how to efficiently insert large amounts of data into PostgreSQL using freely available tools and well-crafted SQL. We'll demonstrate the usage of tools like COPY, how to batch data using multi-valued INSERT statements, functions to look for in language SDKs, and even demonstrate how to use array parameters to speed up multi-valued inserts.
By the end of this session, you will know at least four ways to insert bulk data, the impact it will have on your PostgreSQL database, and options for improving your current application code to perform at its best!
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2023/schedule/2023/schedule/event/postgresql_bulk_inserts_with_postgresql_four_methods_for_efficient_data_loading/ LOCATION:UA2.118 (Henriot) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Ryan Booz":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:14971@FOSDEM23@fosdem.org TZID:Europe-Brussels DTSTART:20230205T140000 DTEND:20230205T145000 SUMMARY:DBA Evolution (the Changing Role of the Database Administrator) DESCRIPTION:Do you ever find yourself pondering life’s important questions: What does a DBA actually do? How has the role changed over the years? What will it look like in the future? Why are DBAs so grumpy?
It shocked me to realise recently that it’s almost a quarter of a century since I started work as a junior database administrator, fresh out of university. Just like everything else in the IT world, the role of the DBA has evolved massively in that time. Has it changed beyond recognition, or does today’s DBA still do fundamentally the same job?
I don’t imagine most DBAs currently spend their time reorganising their datafiles to create contiguous blocks of free space that the database can make use of. And I’m fairly certain the world is a better place for it.
My 21 year-old self could never have imagined managing a self-healing, automated, scalable database cluster on Kubernetes.
On the other hand, the questions of data modelling, disk capacity, query performance, and user management are as relevant today as they were back then.
Let’s take a light-hearted look at the changing role of the DBA over the past couple of decades, with some guesses about what the DBA of the future will be doing. Or will autonomous databases finally have put us all out of work?
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2023/schedule/2023/schedule/event/postgresql_dba_evolution_the_changing_role_of_the_database_administrator/ LOCATION:UA2.118 (Henriot) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Karen Jex":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:13882@FOSDEM23@fosdem.org TZID:Europe-Brussels DTSTART:20230205T150000 DTEND:20230205T155000 SUMMARY:Deep Dive Into Query Performance DESCRIPTION:If you look at data store as just another service, the things Application cares about is successfully establishing connection and getting results to the queries promptly and with correct results.
In this presentation, we will explore this seemingly simple aspect of working with PostgreSQL in details. We will talk about why you want to go beyond the averages, and how to group queries together in the meaningful way so you’re not overwhelmed with amount of details but find the right queries to focus on.
We will answer the question on when you should focus on tuning specific queries or when it is better to focus on tuning the database (or just getting a bigger box).
We will also look at other ways to minimize user facing response time, such as parallel queries, asynchronous queries, queueing complex work, as well as often misunderstood response time killers such as overloaded network, stolen CPU, and even limits imposed by this pesky speed of light.
CLASS:PUBLIC STATUS:CONFIRMED CATEGORIES:PostgreSQL URL:https:/fosdem.org/2023/schedule/2023/schedule/event/postgresql_deep_dive_into_query_performance/ LOCATION:UA2.118 (Henriot) ATTENDEE;ROLE=REQ-PARTICIPANT;CUTYPE=INDIVIDUAL;CN="Peter Zaitsev":invalid:nomail END:VEVENT BEGIN:VEVENT METHOD:PUBLISH UID:14972@FOSDEM23@fosdem.org TZID:Europe-Brussels DTSTART:20230205T160000 DTEND:20230205T165000 SUMMARY:Don't Do This DESCRIPTION:Based on the legendary "Don't Do This" PostgreSQL wiki page, this talk will explore some of the common pitfalls and misconceptions that Postgres users can face - and show possible ways to undo them or workarounds.
Some of the topics to be covered: