Re: How does Postgres store a B-Tree on disk while using the OS file system?

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Siddharth Jain <siddhsql(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: How does Postgres store a B-Tree on disk while using the OS file system?
Date: 2023-03-07 01:07:29
Message-ID: 22FFB64D-AA07-4E47-A982-3B25743F7E02@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Mar 6, 2023, at 16:24, Siddharth Jain <siddhsql(at)gmail(dot)com> wrote:
> My question: How can it then store a B Tree on disk? I would think storing a B Tree requires storing disk offset addresses and so on (for a node to navigate to another etc.). For this, one would need to write directly to the disk using low-level disk access functions and not use file system API.

All of PostgreSQL's relations (tables and indexes) are stored in files. (They're actually stored in a set of files if it's larger than 1GB, but each relation is treated as one logical file.) The "pointers" in this case are just offsets from the start of that file.

There's some additional information here:

https://www.postgresql.org/docs/current/storage.html

and here:

https://www.postgresql.org/docs/current/btree-implementation.html

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Rowley 2023-03-07 02:51:14 Re: Idea: PostgreSQL equivalent to Oracle's KEEP clause
Previous Message Ron 2023-03-07 00:49:14 Re: How does Postgres store a B-Tree on disk while using the OS file system?