diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-11-27 17:45:25 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-11-28 12:00:12 -0300 |
| commit | e518fa7adfc28e0d0a99fe4e5711386d9a5c6532 (patch) | |
| tree | baf622609b4b8ab79c2c62ee2039468a19c87a84 /src/tutorial/funcs.c | |
| parent | b6ecde8ed4799720eaa1c015e325012dbad095fa (diff) | |
| download | postgresql-e518fa7adfc28e0d0a99fe4e5711386d9a5c6532.tar.gz postgresql-e518fa7adfc28e0d0a99fe4e5711386d9a5c6532.zip | |
Cope with heap_fetch failure while locking an update chain
The reason for the fetch failure is that the tuple was removed because
it was dead; so the failure is innocuous and can be ignored. Moreover,
there's no need for further work and we can return success to the caller
immediately. EvalPlanQualFetch is doing something very similar to this
already.
Report and test case from Andres Freund in
20131124000203.GA4403@alap2.anarazel.de
Diffstat (limited to 'src/tutorial/funcs.c')
0 files changed, 0 insertions, 0 deletions