Re: "Value locking" Wiki page
От | Andres Freund |
---|---|
Тема | Re: "Value locking" Wiki page |
Дата | |
Msg-id | 20141001084955.GZ2084@awork2.anarazel.de обсуждение исходный текст |
Ответ на | "Value locking" Wiki page (Peter Geoghegan <pg@heroku.com>) |
Ответы |
Re: "Value locking" Wiki page
|
Список | pgsql-hackers |
On 2014-10-01 01:44:04 -0700, Peter Geoghegan wrote: > In the hope of unblocking things, I have created this Wiki page, which > details the advantages and disadvantages of all 3 approaches that have > been discussed, as suggested by myself and others: > > https://wiki.postgresql.org/wiki/Value_locking Good. > I actually think that we're only in disagreement on the extent to > which the stated advantages and disadvantages are useful or harmful. > So I think that at the moment this description is a reasonably > balanced handling of the issues. Please add any points that I missed. > > This is by no means complete yet. There is pretty limited handling of > what I call "#3. "Promise" index tuples", because there was no > prototype version of that design, and there are many open questions > about how it would be implemented relative to the other 2 approaches. > Perhaps Andres or Simon would care to improve it. I think I've done a > better job of describing #2, Heikki's design - hardly surprising, > since there was a prototype that we discussed at length - but I'd > appreciate it if other people would make sure that I have everything > right there. This is hopefully the beginning of working the issues > out. I have of course also described my own proposed design alongside > the others. FWIW, Heikki's approach isn't what I'd have choosen, but it's something I can live with. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: