Re: creating gist index seems to look at data ignoring transaction?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Palle Girgensohn <girgen(at)pingpong(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: creating gist index seems to look at data ignoring transaction?
Date: 2019-04-11 14:15:39
Message-ID: 9752.1554992139@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Palle Girgensohn <girgen(at)pingpong(dot)se> writes:
> I noticed some bad data where end < begin, so I modified these first, and tried to vcreate the index in the same transaction. The index creation does not notice the data changes. It seems creating the gist index this is not transaction safe?

Index creation has to include not-yet-dead tuples in case the index gets
used by some transaction that can still see those tuples. So in this
case index entries get made for both the original and the updated versions
of the tuples in question.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-04-11 14:54:20 Re: Zedstore - compressed in-core columnar storage
Previous Message Rafia Sabih 2019-04-11 14:03:39 Re: Zedstore - compressed in-core columnar storage