●Home ●CFP ●Schedule ●Friday, February 22, 2013 ●Saturday, February 23, 2013 ●Sunday, February 24, 2013 ●Special Events ●Information ●Venue ●Exhibitors ●Sponsors ●Speakers ●Presentations ●Video ●Registration ●Promote SCALE The Eleventh Annual Southern California Linux Expo February 22-24, 2013 Hilton Los Angeles International Airport ●Home ●CFP ●Schedule ●Special Events ●Information ●Video ●Registration ●Promote SCALE

Submitting a proper Postgres bug report

Jon Erdman Audience: Intermediate Topic: PostgreSQL In those rare situations when you find a new bug in an opensouce project, the likelihood of getting timely relevant help is often directly related to the quality of your question. Using a real life example of a bug I reported to Postgres, this talk will cover the steps you should follow, including: * Boiling the problem down to a simple case * Confirming it is in fact a new bug * Obtaining the source and creating a debug build * Generating a core dump * Using GDB (with the core) to find and diagnose the crash * Examining the source to determine the cause * Where and how to report it * Following up on your report to help with the fix A good chunk of this should apply to any project, not just Postgres. Room: Century AB Time: Friday, February 22, 2013 - 16:30to17:30