Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Advanced Search Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Troubleshooting PostgreSQL
  • Table Of Contents Toc
  • Feedback & Rating feedback
Troubleshooting PostgreSQL

Troubleshooting PostgreSQL

By : Hans-Jürgen Schönig
4.2 (5)
Buy this Book
close
close
Troubleshooting PostgreSQL

Troubleshooting PostgreSQL

4.2 (5)
By: Hans-Jürgen Schönig
Buy this Book

Overview of this book

If you are a database administrator looking for solutions to common PostgreSQL problems, this is the book for you. The book is suitable for people with intermediate and professional expertise.
Table of Contents (12 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Installing PostgreSQL
Icon
1. Installing PostgreSQL
Icon
Deciding on a version number
Icon
Methods of installing PostgreSQL
Icon
Memory and kernel issues
Icon
Adding checksums to a database instance
Icon
Preventing encoding-related issues
Icon
Avoiding template pollution
Icon
Summary
2
2. Creating Data Structures
Icon
2. Creating Data Structures
Icon
Grouping columns the right way
Icon
Deciding on data types and structure
Icon
Deciding on normalization
Icon
Summary
3
3. Handling Indexes
Icon
3. Handling Indexes
Icon
Understanding indexes in PostgreSQL
Icon
Avoiding trouble with indexes
Icon
Solving common problems
Icon
Handling LIKE queries
Icon
Finding good matches
Icon
Fixing full-text search
Icon
Summary
4
4. Reading Data Efficiently and Correctly
Icon
4. Reading Data Efficiently and Correctly
Icon
Understanding the power of NULL
Icon
Fixing disastrous joins
Icon
Reading large amounts of data
Icon
Understanding prepared queries
Icon
Summary
5
5. Getting Transactions and Locking Right
Icon
5. Getting Transactions and Locking Right
Icon
The PostgreSQL transaction model
Icon
Transaction isolation
Icon
Inspecting locks
Icon
Summary
6
6. Writing Proper Procedures
Icon
6. Writing Proper Procedures
Icon
Choosing the right language
Icon
Managing procedures and transactions
Icon
Procedures and indexing
Icon
Understanding memory
Icon
Summary
7
7. PostgreSQL Monitoring
Icon
7. PostgreSQL Monitoring
Icon
Checking the overall database behavior
Icon
Detecting I/O bottlenecks
Icon
Checking for conflicts
Icon
Chasing down slow queries
Icon
Inspecting internal information
Icon
Integrating with external tools
Icon
Alternative tools
Icon
Summary
8
8. Fixing Backups and Replication
Icon
8. Fixing Backups and Replication
Icon
Using pg_dump
Icon
Managing point-in-time recovery
Icon
Making use of asynchronous replication
Icon
Switching to synchronous replication
Icon
Handling timelines
Icon
Summary
9
9. Handling Hardware and Software Disasters
chevron up
Icon
9. Handling Hardware and Software Disasters
Icon
Checksums – preventing silent corruption
Icon
Zeroing out damaged pages
Icon
Dealing with index corruption
Icon
Dumping individual pages
Icon
Resetting the transaction log
Icon
Power-out-related issues
Icon
Summary
10
10. A Standard Approach to Troubleshooting
Icon
10. A Standard Approach to Troubleshooting
Icon
Getting an overview of the problem
Icon
Attacking low performance
Icon
Fixing common replication issues
Icon
Summary
11
Index
Icon
Index

Zeroing out damaged pages

Once in a while, things do go wrong even if all precautions have been taken. A filesystem might lose some blocks here and there or a disk might simply lose a couple of sectors. The following might happen on the PostgreSQL side in this case:

test=# SELECT count(*) FROM t_test;
ERROR:  invalid page in block 535 of relation 
    base/16384/16436

If a block (or a couple of blocks) has fallen victim to a problem in the filesystem, PostgreSQL will error out and tell the end user that the query cannot be completed anymore.

In the scenario outlined here, you can be certain of one thing: some data has been lost in the storage system. It is important to point out that loss of data is virtually never caused by PostgreSQL itself. In most cases, we are talking about broken hardware, broken filesystems, or some other memory-related problem that has spread its blessings to your data files.

If storage-related problems arise, the general rule is, "don't touch stuff; back up stuff!"...

Visually different images
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Troubleshooting PostgreSQL
End of Section 9
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon