diff options
author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2012-10-31 11:05:28 -0300 |
---|---|---|
committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2012-10-31 11:05:28 -0300 |
commit | 9b8dd7e8aa19e6145a996cfc881b5617f497632d (patch) | |
tree | 8a487c4d23552ce45b9a382a834cd8d4f9a7e09b /src/backend/access/gist/gistbuildbuffers.c | |
parent | 04f28bdb8477ad48c7f9987950595764eae3218e (diff) | |
download | postgresql-9b8dd7e8aa19e6145a996cfc881b5617f497632d.tar.gz postgresql-9b8dd7e8aa19e6145a996cfc881b5617f497632d.zip |
Fix erroneous choices of segNo variables
Commit dfda6eba (which changed segment numbers to use a single 64 bit
variable instead of log/seg) introduced a couple of bogus choices of
exactly which log segment number variable to use in each case.
This is currently pretty harmless; in one place, the bogus number was
only being used in an error message for a pretty unlikely condition
(failure to fsync a WAL segment file). In the other, it was using a
global variable instead of the local variable; but all callsites were
passing the value of the global variable anyway.
No need to backpatch because that commit is not on earlier branches.
Diffstat (limited to 'src/backend/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions