diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-11-27 17:50:33 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2013-11-28 11:54:25 -0300 |
| commit | 4c71f48f4c6c923d1b3f6e6c788e8a0995f4241a (patch) | |
| tree | 94c9906206249f18b528f887b12e9ca336daeb6c /src/tutorial/funcs.c | |
| parent | 2a4b6eed0916a8fdc57b4778ecb1463fe752d369 (diff) | |
| download | postgresql-4c71f48f4c6c923d1b3f6e6c788e8a0995f4241a.tar.gz postgresql-4c71f48f4c6c923d1b3f6e6c788e8a0995f4241a.zip | |
Use a more granular approach to follow update chains
Instead of simply checking the KEYS_UPDATED bit, we need to check
whether each lock held on the future version of the tuple conflicts with
the lock we're trying to acquire.
Per bug report #8434 by Tomonari Katsumata
Diffstat (limited to 'src/tutorial/funcs.c')
0 files changed, 0 insertions, 0 deletions