Investigating and reporting a bug
When you find out that PostgreSQL is not doing what it should, then it's time to investigate.
Getting ready
It is a good idea to make a full copy of your PostgreSQL installation before you start investigating. This will help you restart several times and be sure that you are actually investigating the results of the bug, and not chasing your own tail by looking at changes introduced by your last investigation and debugging attempt.
Do not forget to include your tablespaces too in the full copy.
How to do it…
Try to make a minimal repeatable test scenario that exhibits this bug. Sometimes, the bug disappears while doing this, but mostly it is needed for making the process easy. It is almost impossible to fix a bug that ...
Get PostgreSQL 9 Administration Cookbook - Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
