| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | lars hofhansl <lhofhansl(at)yahoo(dot)com> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Ivan Voras <ivoras(at)freebsd(dot)org>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: UPDATEDs slowing SELECTs in a fully cached database |
| Date: | 2011-08-05 09:58:46 |
| Message-ID: | CAMkU=1yETnhs1dpiZH0BKWAnCG_63pF1xMbXaegvhuz6-kRiDQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 7/29/11, lars hofhansl <lhofhansl(at)yahoo(dot)com> wrote:
> Thanks Pavan!
>
>
> I think the most important points are still that:
> 1. The WAL write should be happening asynchronously (if that is possible)
I think it is agreed that this is a "todo"; but since you reported
that turning off synchronous commit did not improve performance, it is
not directly relevant for you.
> 2. There should be an option do not perform these compactions if the page is
> only touched by reads.
If the page is only touched by reads, there would be nothing to compact.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vitalii Tymchyshyn | 2011-08-05 10:36:38 | Re: Performance die when COPYing to table with bigint PK |
| Previous Message | Robert Ayrapetyan | 2011-08-05 08:44:04 | Re: Performance die when COPYing to table with bigint PK |