Re: installing Oracle on Debian AMD64
- To: debian-amd64 <firstname.lastname@example.org>
- Subject: Re: installing Oracle on Debian AMD64
- From: Anthony DeRobertis <email@example.com>
- Date: Thu, 03 Nov 2005 22:15:06 -0500
- Message-id: <[🔎] 436AD23A.firstname.lastname@example.org>
- In-reply-to: <436669D9.email@example.com>
- References: <Pine.LNX.4.62.0510231242030.10230@Chrestomanci> <firstname.lastname@example.org> <435E7668.email@example.com> <20051025190100.GC9057@csclub.uwaterloo.ca> <435E8CC3.firstname.lastname@example.org> <[🔎] 20051031144129.GA9486@csclub.uwaterloo.ca> <43664ACC.email@example.com> <firstname.lastname@example.org> <436669D9.email@example.com>
Sven Mueller wrote:
>>>>It is also easier to be fast writing if you lock the
>>>>whole table and prevent others from accessing it while you update
>>>>things. Slows down reading to stopped while you do a write though.
>>More like stops every other read and write.
> for as long as the write takes.
If only that were true! But, instead, it blocks everything for as long
as the write takes *plus* as long as all the reads that started before
the write was issued take.
(At least by default. I know about the low priority writes option, but
that has its own problems, like the writes never happening.)