Re: Parallel Sort
От | Tom Lane |
---|---|
Тема | Re: Parallel Sort |
Дата | |
Msg-id | 16083.1368592203@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Parallel Sort (Hannu Krosing <hannu@krosing.net>) |
Ответы |
Re: Parallel Sort
|
Список | pgsql-hackers |
Hannu Krosing <hannu@krosing.net> writes: > Has anybody looked into making syscache MVCC compliant ? This is the wrong statement of the question. The right statement is "how would you like backend A to be updating table T in compliance with a view of table T's schema that is obsolete because of backend B's already-committed DDL changes?" For example, ignoring a just-committed CHECK constraint because it's not visible to your transaction's snapshot. The point of SnapshotNow catalog lookups is to be sure that we see the current definition of a table whether or not we're in a transaction whose snapshot precedes the last DDL change to that table. There might be some other way to deal with that consistency problem, but just changing syscache's behavior is not going to make things better. regards, tom lane
В списке pgsql-hackers по дате отправления: