Re: Running a query twice to ensure cached results.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Luke Lonergan" <llonergan(at)greenplum(dot)com>
Cc: "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Running a query twice to ensure cached results.
Date: 2006-06-13 15:01:40
Message-ID: 22825.1150210900@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Luke Lonergan" <llonergan(at)greenplum(dot)com> writes:
> What you are seeing is the now infamous "Postgres writes a table one more
> time after loading" behavior.

> Tom - can you explain what's going on with this?

Setting XMIN_COMMITTED hint bits.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2006-06-13 15:09:19 Re: CSV mode option for pg_dump
Previous Message Andrew Dunstan 2006-06-13 14:52:38 Re: CSV mode option for pg_dump