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

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #13429: Update 0 rows for matching record
Дата
Msg-id CAKFQuwZczMuyjiJvjTsySM-D3iCMN8M5eV1b3DvfRMTsLFmOpw@mail.gmail.com
обсуждение исходный текст
Ответ на BUG #13429: Update 0 rows for matching record  (smoola@travelclick.com)
Список pgsql-bugs
On Wed, Jun 10, 2015 at 12:19 PM, <smoola@travelclick.com> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      13429
> Logged by:          Sandeep Moola
> Email address:      smoola@travelclick.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 wa=
s
> 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=3D10060451491;
>  yrd_cuttoff
> -------------
>  N
> (1 row)
>
> STEP2:
> UPDATE yrd_yield_room_details SET yrd_cuttoff=3D'NC' WHERE
> yrd_yrd_key=3D10060451491;
> UPDATE 0
>
> STEP3:
> SELECT yrd_cuttoff FROM yrd_yield_room_details WHERE
> yrd_yrd_key=3D10060451491;
>  yrd_cuttoff
> -------------
>  N
>
>
=E2=80=8BThis 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"?

=E2=80=8BDavid J.=E2=80=8B

В списке pgsql-bugs по дате отправления:

Предыдущее
От: smoola@travelclick.com
Дата:
Сообщение: BUG #13429: Update 0 rows for matching record
Следующее
От: "David G. Johnston"
Дата:
Сообщение: Re: BUG #13426: table bloat - dead rows not removed after vacuum