Re: [HACKERS] non-functional update notice unneccesarily - Mailing list pgsql-hackers

From Thomas G. Lockhart
Subject Re: [HACKERS] non-functional update notice unneccesarily
Date
Msg-id 35506E49.B75665B6@alumni.caltech.edu
Whole thread Raw
In response to non-functional update notice unneccesarily  (Brett McCormickS <brett@abraxas.scene.com>)
List pgsql-hackers
> update mempayment set paywho = 'icvproxy' from do_addpayment where dappays
> eq = payseqid;
> NOTICE:  Non-functional update, only first update is performed
> UPDATE 31
>
> more than one update was indeed performed..

This is a confusing message, but I think it means that the
parser/planner/optimizer decided to simplify your over-specified or
redundant query. Don't know enough details about your tables and query
to know for sure in this case, but you can see examples of this in the
regression test suite.

                    - Tom

pgsql-hackers by date:

Previous
From: Michael Meskes
Date:
Subject: initdb still doesn't work
Next
From: The Hermit Hacker
Date:
Subject: Re: AW: [HACKERS] Re: [QUESTIONS] groups of users