Re: Inadequate thought about buffer locking during hot standby replay
| От | Robert Haas |
|---|---|
| Тема | Re: Inadequate thought about buffer locking during hot standby replay |
| Дата | |
| Msg-id | CA+Tgmob6NS=jhz=y6NYnfqmfW5y6ten5YXi3WMOc9v3vwgkMCA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Inadequate thought about buffer locking during hot standby replay (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Inadequate thought about buffer locking during hot standby replay
|
| Список | pgsql-hackers |
On Sun, Nov 11, 2012 at 6:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > I already pointed out the inconsistency in heap_xlog_freeze about > whether a cleanup lock is needed. As is, this patch uses a cleanup > lock, but I suspect that a regular lock is sufficient --- comments? Well, according to storage/buffer/README: 1. To scan a page for tuples, one must hold a pin and either shared or exclusive content lock. To examine the commit status (XIDs and status bits) of a tuple in a shared buffer, one must likewise hold a pin and either shared or exclusive lock. That does indeed make it sound like an x-lock is enough. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: