Impact of table scan on shared buffers

From: "Morris Goldstein" <morris(dot)x(dot)goldstein(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Impact of table scan on shared buffers
Date: 2007-11-13 22:10:33
Message-ID: 41b6f5c20711131410s59f688dfw86e7faa089aab4c5@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Suppose I have a large table with no indexes, and I scan the entire
thing. What is the impact on the shared buffers? I'm interested in
three scenarios:

- Scan done in SQL using SELECT, (via JDBC if it matters).
- Scan done using SQL COPY.
- Scan done using psql COPY.

I suspect that the SELECT scan will tend to displace everything else
in shared buffers, and I hope that the two forms of COPY do not. Is
that correct?

I'm using 7.4 now, but I'm also interested in the answer for 8.x.

Morris

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jeff Davis 2007-11-13 22:30:01 Re: Impact of table scan on shared buffers
Previous Message Steve Crawford 2007-11-13 20:35:26 Path to top of tree