Re: Full page images in WAL & Cache Invalidation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Full page images in WAL & Cache Invalidation
Date: 2007-07-22 21:26:03
Message-ID: 4715.1185139563@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Florian G. Pflug" <fgp(at)phlo(dot)org> writes:
> Tom Lane wrote:
>> The real problem with the scheme you propose is that it turns a
>> cache flush on one table into a system-wide cache flush.

> Yes.. It really builds on the idea that those flushes happen not
> too frequently.

The problem is that flushes may be infrequent for any one table,
but if you use an implementation that converts every per-table
flush to a system-wide flush, it's not so infrequent anymore.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-07-22 21:42:14 Re: Full page images in WAL & Cache Invalidation
Previous Message Florian G. Pflug 2007-07-22 20:51:14 Re: Full page images in WAL & Cache Invalidation