Re: [HACKERS] non-functional update notice unneccesarily

From: "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu>
To: Brett McCormickS <brett(at)abraxas(dot)scene(dot)com>
Cc: pgsql-hackers(at)hub(dot)org
Subject: Re: [HACKERS] non-functional update notice unneccesarily
Date: 1998-05-06 14:06:01
Message-ID: 35506E49.B75665B6@alumni.caltech.edu
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 1998-05-06 15:37:59 Re: AW: [HACKERS] Re: [QUESTIONS] groups of users
Previous Message Michael Meskes 1998-05-06 12:31:44 initdb still doesn't work