From: jacktby@gmail.com <jacktby@gmail.com>
To: pgsql-general <pgsql-general@lists.postgresql.org>
Subject: How does pg index page optimize dead tuples?
Date: Thu, 20 Apr 2023 09:41:52 +0800
Message-ID: <2023042009415111127413@gmail.com> (raw)
As far as I know, when a index page is full, if you insert a new tuple here, you will split it into two pages.
But pg won't delete the half tuples in the old page in real. So if there is another tuple inserted into this old
page, will pg split it again? I think that's not true, so how it solve this one? please give me a code example,thanks.
jacktby@gmail.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: jacktby@gmail.com
Subject: Re: How does pg index page optimize dead tuples?
In-Reply-To: <2023042009415111127413@gmail.com>
References: <2023042009415111127413@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox