diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2011-10-20 19:43:31 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2011-10-20 19:43:45 -0400 |
commit | d1d094e4cf7d80cb2b4f68b5e8ce11aa9ebcbf3c (patch) | |
tree | 4bfc68c15afd421339f218e72a60308ccf405523 /src/backend/executor/nodeFunctionscan.c | |
parent | 790fa1fdd8bb32e2e9055dd47d76c2382c51c84a (diff) | |
download | postgresql-d1d094e4cf7d80cb2b4f68b5e8ce11aa9ebcbf3c.tar.gz postgresql-d1d094e4cf7d80cb2b4f68b5e8ce11aa9ebcbf3c.zip |
Simplify and improve ProcessStandbyHSFeedbackMessage logic.
There's no need to clamp the standby's xmin to be greater than
GetOldestXmin's result; if there were any such need this logic would be
hopelessly inadequate anyway, because it fails to account for
within-database versus cluster-wide values of GetOldestXmin. So get rid of
that, and just rely on sanity-checking that the xmin is not wrapped around
relative to the nextXid counter. Also, don't reset the walsender's xmin if
the current feedback xmin is indeed out of range; that just creates more
problems than we already had. Lastly, don't bother to take the
ProcArrayLock; there's no need to do that to set xmin.
Also improve the comments about this in GetOldestXmin itself.
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions