|
|
|
repeatable read "will not necessarily always be consistent". Это как ?
|
|||
|---|---|---|---|
|
#18+
Всем доброго дня. Читаю доку: http://www.postgresql.org/docs/9.3/interactive/transaction-iso.html The Repeatable Read mode provides a rigorous guarantee that each transaction sees a completely stable view of the database. However, this view will not necessarily always be consistent with some serial (one at a time) execution of concurrent transactions of the same level. For example, even a read only transaction at this level may see a control record updated to show that a batch has been completed but not see one of the detail records which is logically part of the batch because it read an earlier revision of the control record. Attempts to enforce business rules by transactions running at this isolation level are not likely to work correctly without careful use of explicit locks to block conflicting transactions. Вопрос: есть какой-то sql-скрипт, показывающий проблему (см. выделенный текст) ? Вот здесь показан DDL двух таблиц, а дальше - только "блаблала". Пытаюсь сделать то, что они там пишут - не выходит: окно-1 Код: sql 1. 2. 3. 4. 5. 6. 7. 8. 9. окно-2 Код: sql 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Ну, и где тут "may see a control record updated to show that a batch has been completed but not see one of the detail records" ? ... |
|||
|
:
Нравится:
Не нравится:
|
|||
| 13.11.2014, 20:37:35 |
|
||
|
|

start [/forum/topic.php?fid=53&msg=38805479&tid=1998357]: |
0ms |
get settings: |
9ms |
get forum list: |
11ms |
check forum access: |
2ms |
check topic access: |
2ms |
track hit: |
53ms |
get topic data: |
10ms |
get forum data: |
3ms |
get page messages: |
51ms |
get tp. blocked users: |
1ms |
| others: | 244ms |
| total: | 386ms |

| 0 / 0 |
