| From: | Tim Schwenke <tim(at)trallnag(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "Pgsql Novice" <pgsql-novice(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Does PostgreSQL cache all columns of a table after SELECT? |
| Date: | 2023-06-05 15:15:24 |
| Message-ID: | 1888c20926e.d2fc55ae8791.8729366224157085719@trallnag.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Thanks, you all helped me
---- On Mon, 05 Jun 2023 16:26:08 +0200 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote ---
On Mon, Jun 5, 2023, 06:17 Tim Schwenke <mailto:tim(at)trallnag(dot)com> wrote:
Hello David,
from what I understand, in PostgreSQL, tables are stored in one or more files called segments. There is no separation by columns.
https://www.postgresql.org/docs/8.1/storage.html
This means if I select a single column from a table the first time, the full file / segment is read and put into page cache if there is enough space.
Pages are subsegment.
You may also wish to take care to notice the version of documentation pages you look at and reference. 8.1 is long past its expiration date.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim Schwenke | 2023-06-05 15:30:32 | Will PostgreSQL use normal and huge pages at the same time? |
| Previous Message | David G. Johnston | 2023-06-05 14:26:08 | Re: Does PostgreSQL cache all columns of a table after SELECT? |