Re: [BUG?] UPDATE with RETURNING tableoid

From: KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [BUG?] UPDATE with RETURNING tableoid
Date: 2008-12-17 01:42:33
Message-ID: 49485909.9010807@ak.jp.nec.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com> writes:
>> I found a strange behavior on the recent v8.4devel with/without
>> SE-PostgreSQL patch set. Can you reproduce the following behavior?
>
>> When I use UPDATE statement with RETURNING clause which contains
>> references to "tableoid" system column, it returns InvalidOid.
>> (The correct valus is 16384 in this case.)
>> However, RETURNING clause with INSERT/DELETE statement works well.
>
> Confirmed here, all the way back to 8.2. I concur it's a bug.

http://git.postgresql.org/?p=postgresql.git;a=commitdiff;h=ab7c31031eb4c9fa73d92c19d55a8c7f8bbf4196

Thanks, I confirmed the update eliminates the bug.
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai(at)ak(dot)jp(dot)nec(dot)com>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2008-12-17 01:57:47 Re: Another issue in default-values patch: defaults expanded too soon
Previous Message Tom Lane 2008-12-17 01:39:17 Re: Another issue in default-values patch: defaults expanded too soon