Skip site navigation (1) Skip section navigation (2)

pgsql: When a GiST page is split during index build,it might not have

From: Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: When a GiST page is split during index build,it might not have
Date: 2012-03-02 11:25:23
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
When a GiST page is split during index build, it might not have a buffer.

Previously it was thought that it's impossible as the code stands, because
insertions create buffers as tuples are cascaded downwards, and index
split also creaters buffers eagerly for all halves. But the example from
Jay Levitt demonstrates that it can happen, when the root page is split.
It's in fact OK if the buffer doesn't exist, so we just need to remove the
sanity check. In fact, we've been discussing the possibility of destroying
empty buffers to conserve memory, which would render the sanity check
completely useless anyway.

Fix by Alexander Korotkov



Modified Files
src/backend/access/gist/gistbuildbuffers.c |    8 ++------
1 files changed, 2 insertions(+), 6 deletions(-)

pgsql-committers by date

Next:From: Magnus HaganderDate: 2012-03-02 11:33:54
Subject: pgsql: Add a rule to optionally build docs with the stylesheet fromthe
Previous:From: Peter EisentrautDate: 2012-03-01 19:18:44
Subject: pgsql: Small possible clarification in pg_basebackup reference page

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group