diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-06-29 00:51:44 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-06-29 00:51:44 -0400 |
| commit | 3ac860f6b33ffa0733d4d013718c5f408282fcb6 (patch) | |
| tree | 7c76c1eabb9c24b98bccfa3f9caa006911fda729 /src/backend/access/transam/xlog.c | |
| parent | 8a9bcf7f5c39e4cc30be0478065853619d61fec8 (diff) | |
| download | postgresql-3ac860f6b33ffa0733d4d013718c5f408282fcb6.tar.gz postgresql-3ac860f6b33ffa0733d4d013718c5f408282fcb6.zip | |
Fix NOTIFY to cope with I/O problems, such as out-of-disk-space.
The LISTEN/NOTIFY subsystem got confused if SimpleLruZeroPage failed,
which would typically happen as a result of a write() failure while
attempting to dump a dirty pg_notify page out of memory. Subsequently,
all attempts to send more NOTIFY messages would fail with messages like
"Could not read from file "pg_notify/nnnn" at offset nnnnn: Success".
Only restarting the server would clear this condition. Per reports from
Kevin Grittner and Christoph Berg.
Back-patch to 9.0, where the problem was introduced during the
LISTEN/NOTIFY rewrite.
Diffstat (limited to 'src/backend/access/transam/xlog.c')
0 files changed, 0 insertions, 0 deletions