Re: [HACKERS] Bogus "Non-functional update" notices

From: Vadim Mikheev <vadim(at)krs(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Bogus "Non-functional update" notices
Date: 1998-07-28 02:57:35
Message-ID: 35BD3E1F.D5E8CD8A@krs.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> I have only seen this happen when the UPDATE was using an index scan to
> find the tuples to update (the table in this example has a btree index
> on oid). So, somehow the index is returning the same tuple more than
> once.

In UPDATE backend inserts index tuple for new version of heap tuple
and adjusts all index scans affected by this insertion.
Something is wrong in nbtscan.c:_bt_adjscans()...

Vadim

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Aleksey Demakov 1998-07-28 06:45:13 Re: [INTERFACES] psqlodbc
Previous Message Thomas G. Lockhart 1998-07-28 02:22:13 psqlodbc