Re: BUG #13429: Update 0 rows for matching record

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: smoola(at)travelclick(dot)com
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13429: Update 0 rows for matching record
Date: 2015-06-10 17:10:36
Message-ID: CAKFQuwZczMuyjiJvjTsySM-D3iCMN8M5eV1b3DvfRMTsLFmOpw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Jun 10, 2015 at 12:19 PM, <smoola(at)travelclick(dot)com> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 13429
> Logged by: Sandeep Moola
> Email address: smoola(at)travelclick(dot)com
> PostgreSQL version: 9.2.8
> Operating system: Red Hat Enterprise Linux Server release 6.5
> Description:
>
> We were trying to update a record in our database as below and the row was
> not getting updated. No error was shown neither on the command promt nor in
> the logs
> STEP1:
> SELECT yrd_cuttoff FROM yrd_yield_room_details WHERE
> yrd_yrd_key=10060451491;
> yrd_cuttoff
> -------------
> N
> (1 row)
>
> STEP2:
> UPDATE yrd_yield_room_details SET yrd_cuttoff='NC' WHERE
> yrd_yrd_key=10060451491;
> UPDATE 0
>
> STEP3:
> SELECT yrd_cuttoff FROM yrd_yield_room_details WHERE
> yrd_yrd_key=10060451491;
> yrd_cuttoff
> -------------
> N
>
>
​This is not likely to be a bug but in any case if you are not able to
supply a self-contained test case, or the actual schema involved, figuring
out where you likely have a problem is going to be difficult.

As a first stab: are there any triggers on "yrd_yield_room_details"?

​David J.​

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2015-06-10 17:13:24 Re: BUG #13426: table bloat - dead rows not removed after vacuum
Previous Message smoola 2015-06-10 16:19:19 BUG #13429: Update 0 rows for matching record