Presented by:

02035371a85c64f570f3f0ea03893ad5

Jim Mlodgenski

OpenSCG

Jim has more than 20 years of experience developing data intensive applications and infrastructure. Prior to joining OpenSCG, Jim was CEO at StormDB, a Postgres-XC scalable public cloud solution. While at StormDB, Jim envisioned the offering and was responsible for all product development. Prior to StormDB, Jim was chief architect at EnterpriseDB, leading the firm’s technology direction, including its early cloud offerings and other product lines. Jim also very active in the PostgreSQL community, co-founding both the New York and Philadelphia PostgreSQL Meetup groups, co-organizing the largest PostgreSQL conferences, and serving on the Board of the PostgreSQL Foundation. Jim also speaks regularly at PostgreSQL and other open sources conferences.

No video of the event yet, sorry!

We have all heard about this dreaded thing in PostgreSQL called vacuum, but what is it really and why do we need to do it. In this talk, we will talk about why PostgreSQL needs to vacuum tables and how to manage it. It will focus on configuring autovacuum properly for your application. In the end, you will understand how and why to set things like autovacuum_vacuum_threshold and autovacuum_max_workers.

Date:
2017 October 3 15:30
Duration:
50 min
Room:
Alternate room
Conference:
South Africa 2017
Language:
Track:
Postgres
Difficulty:
Medium