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 12:00:12 -0300 |
| commit | 247c76a989097f1b4ab6fae898f24e75aa27fc1b (patch) | |
| tree | fd5adb45900ea946da30bfd63dade5e3e6e6d2ad /src/backend/tcop/postgres.c | |
| parent | e4828e9ccba731178dd77aed078db7ceb0e1e8d1 (diff) | |
| download | postgresql-247c76a989097f1b4ab6fae898f24e75aa27fc1b.tar.gz postgresql-247c76a989097f1b4ab6fae898f24e75aa27fc1b.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/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions