Re: SPGist "triple parity" concept doesn't work
От
Greg Stark
Тема
Re: SPGist "triple parity" concept doesn't work
Дата
Msg-id
CAM-w4HPV5uqrFpo4=N44H3BYObqiRDtkbFELgqJCPq6QGPsLjA@mail.gmail.com
Ответ на
SPGist "triple parity" concept doesn't work (Tom Lane)
Список
Дерево обсуждения
SPGist "triple parity" concept doesn't work Tom Lane <tgl@sss.pgh.pa.us>
Re: SPGist "triple parity" concept doesn't work Alvaro Herrera <alvherre@2ndquadrant.com>
Re: SPGist "triple parity" concept doesn't work Tom Lane <tgl@sss.pgh.pa.us>
Re: SPGist "triple parity" concept doesn't work Teodor Sigaev <teodor@sigaev.ru>
Re: SPGist "triple parity" concept doesn't work Tom Lane <tgl@sss.pgh.pa.us>
Re: SPGist "triple parity" concept doesn't work Teodor Sigaev <teodor@sigaev.ru>
Re: SPGist "triple parity" concept doesn't work Teodor Sigaev <teodor@sigaev.ru>
Re: SPGist "triple parity" concept doesn't work Tom Lane <tgl@sss.pgh.pa.us>
Re: SPGist "triple parity" concept doesn't work Greg Stark <stark@mit.edu>
Re: SPGist "triple parity" concept doesn't work Tom Lane <tgl@sss.pgh.pa.us>
Re: SPGist "triple parity" concept doesn't work Will Crawford <billcrawford1970@gmail.com>
On Thu, Jun 6, 2013 at 10:46 PM, Tom Lane wrote: > To prevent > : deadlocks we introduce a concept of "triple parity" of pages: if inner tuple > : is on page with BlockNumber N, then its child tuples should be placed on the > : same page, or else on a page with BlockNumber M where (N+1) mod 3 == M mod 3. > : This rule guarantees that tuples on page M will have no children on page N, > : since (M+1) mod 3 != N mod 3. Even if the invariant was maintained why doesn't that just mean you need three concurrent inserts to create a deadlock? -- greg
В списке pgsql-hackers по дате отправления