diff options
| author | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2010-11-02 11:23:43 +0200 |
|---|---|---|
| committer | Heikki Linnakangas <heikki.linnakangas@iki.fi> | 2010-11-02 11:39:48 +0200 |
| commit | 8c843fff2d8db7889b81782ab4f3324cbda4ed2a (patch) | |
| tree | 4e077881b96aed36906cc344521344817b5f941a /src/backend/access/gist | |
| parent | 0811ff2063be973953eda89e76dac0d299f0fb6b (diff) | |
| download | postgresql-8c843fff2d8db7889b81782ab4f3324cbda4ed2a.tar.gz postgresql-8c843fff2d8db7889b81782ab4f3324cbda4ed2a.zip | |
Bootstrap WAL to begin at segment logid=0 logseg=1 (000000010000000000000001)
rather than 0/0, so that we can safely use 0/0 as an invalid value. This is a
more future-proof fix for the corner-case bug in streaming replication that
was fixed yesterday. We had a similar corner-case bug with log/seg 0/0 back in
February as well. Avoiding 0/0 as a valid value should prevent bugs like that
in the future. Per Tom Lane's idea.
Back-patch to 9.0. Since this only affects bootstrapping, it makes no
difference to existing installations. We don't need to worry about the
bug in existing installations, because if you've managed to get past the
initial base backup already, you won't hit the bug in the future either.
Diffstat (limited to 'src/backend/access/gist')
0 files changed, 0 insertions, 0 deletions