From: | Hannu Krosing <hannu(at)trust(dot)ee> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Don Baccus <dhogaza(at)pacifier(dot)com>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Priorities for 6.6 |
Date: | 1999-06-05 20:51:32 |
Message-ID: | 37598DD4.62C56219@trust.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>
> Don Baccus <dhogaza(at)pacifier(dot)com> writes:
> > While I don't doubt your analysis is correct for the case you've
> > uncovered, it doesn't explain why surrounding a bunch of selects
> > with a begin/end block greatly descreases disk activity for tables
> > that don't change.
>
> Hmm, I'm not sure why that should be, either. Anyone?
>From a recent discussion I remember that every block that is read
in is marked as dirty, regardless of weather it is modified or not.
It is not a genuine bug (as it only slows thong down instead of
getting wrong results), but still a misfeature.
It is most likely an ancient quickfix for some execution path that
failed to set the dirty mark when it should have.
---------------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-06-05 20:58:23 | Re: [HACKERS] Priorities for 6.6 |
Previous Message | Bruce Momjian | 1999-06-05 19:10:42 | Re: [PATCHES] Re: contrib code for 6.5 |