[COMMITTERS] pgsql: Fix wrong WAL info value generated when gistContinueInsert()

2009-12-24 Thread Tom Lane
Log Message: --- Fix wrong WAL info value generated when gistContinueInsert() performs an index page split. This would result in index corruption, or even more likely an error during WAL replay, if we were unlucky enough to crash during end-of-recovery cleanup after having completed an inc

[COMMITTERS] pgsql: Fix wrong WAL info value generated when gistContinueInsert()

2009-12-24 Thread Tom Lane
Log Message: --- Fix wrong WAL info value generated when gistContinueInsert() performs an index page split. This would result in index corruption, or even more likely an error during WAL replay, if we were unlucky enough to crash during end-of-recovery cleanup after having completed an inc

[COMMITTERS] pgsql: Fix wrong WAL info value generated when gistContinueInsert()

2009-12-24 Thread Tom Lane
Log Message: --- Fix wrong WAL info value generated when gistContinueInsert() performs an index page split. This would result in index corruption, or even more likely an error during WAL replay, if we were unlucky enough to crash during end-of-recovery cleanup after having completed an inc

[COMMITTERS] pgsql: Fix wrong WAL info value generated when gistContinueInsert()

2009-12-24 Thread Tom Lane
Log Message: --- Fix wrong WAL info value generated when gistContinueInsert() performs an index page split. This would result in index corruption, or even more likely an error during WAL replay, if we were unlucky enough to crash during end-of-recovery cleanup after having completed an inc