Depending on the project, debugging can take 50 to 90% of development time. But it gets less than 2% of the press. PostgreSQL has great tools for debugging, but they are most effective when deployed as part of an overall strategy.
We will look at strategies for debugging PostgreSQL: how to find bugs, how to fix them, and how to keep them from happening in the first place.
We’ll look at root causes, technical tricks, and scientific strategies, and why — even if you can’t always write perfect code — it is usually a good idea to try.
We’ll hear from Bjarne Stroustrup, Sherlock Holmes, Kernighan and Ritchie, Pogo, & the experts of the PostgreSQL community.
Goal: less time debugging, more time building great tools and apps that stay up & get the job done.