Bruce Momjian wrote:
>
> > In short, if you load a bunch of tuples into a table, the first select
> > after the load can run a lot slower than you might expect, because it'll
> > be writing back most or all of the pages it touches. But that penalty
> > doesn't affect every select, only the first one to scan a newly-written
> > tuple.
>
> I have removed this from the TODO list:
>
> * Prevent fsync in SELECT-only queries
When selecting (i.e. - read-only) transaction commits,
it change pg_log - we obviously can avoid this!
No sense to store commit/abort status of read-only xactions!
Vadim
