Re: Parallel Seq Scan vs kernel read ahead
От | Robert Haas |
---|---|
Тема | Re: Parallel Seq Scan vs kernel read ahead |
Дата | |
Msg-id | CA+TgmoYS6109DHMpa8VG=PmgX8UTSm=83RbCNtXr9G9j0A2paQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Parallel Seq Scan vs kernel read ahead (Ranier Vilela <ranier.vf@gmail.com>) |
Ответы |
Re: Parallel Seq Scan vs kernel read ahead
Re: Parallel Seq Scan vs kernel read ahead |
Список | pgsql-hackers |
Ranier, This topic is largely unrelated to the current thread. Also... On Mon, Jun 22, 2020 at 12:47 PM Ranier Vilela <ranier.vf@gmail.com> wrote: > Questions: > 1. Why acquire and release lock in retry: loop. This is a super-bad idea. Note the coding rule mentioned in spin.h. There are many discussion on this mailing list about the importance of keeping the critical section for a spinlock to a few instructions. Calling another function that *itself acquires an LWLock* is definitely not OK. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: