| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> |
| Cc: | Ian Barwick <ian(at)2ndquadrant(dot)com>, Tom Dunstan <pgsql(at)tomd(dot)cc>, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: "RETURNING PRIMARY KEY" syntax extension |
| Date: | 2014-07-01 14:13:23 |
| Message-ID: | CA+TgmoY6Q9QTpSOjBe-FORQRs6xUXN6V9i2dYBYYi3Suchq2KA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 1, 2014 at 8:00 AM, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com> wrote:
> .) In map_primary_key_to_list() patch using INDEX_ATTR_BITMAP_IDENTITY_KEY
> bitmap to get the keycols. In IndexAttrBitmapKind there is also
> INDEX_ATTR_BITMAP_KEY, so was confuse between INDEX_ATTR_BITMAP_KEY and
> INDEX_ATTR_BITMAP_IDENTITY_KEY and also haven't found related comments in
> the code. Later with use of testcase and debugging found confirmed that
> INDEX_ATTR_BITMAP_IDENTITY_KEY only returns the Primary key.
Actually, that depends on how REPLICA IDENTITY is set. IOW, you can't
assume that will give you the primary key.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-07-01 14:39:04 | Re: avoiding tuple copying in btree index builds |
| Previous Message | Kevin Grittner | 2014-07-01 14:05:37 | Re: Patch to send transaction commit/rollback stats to the stats collector unconditionally. |