| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, zam6ak(at)gmail(dot)com, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14813: pg_get_serial_sequence does not return seqence name for IDENTITY columns |
| Date: | 2017-09-14 21:15:53 |
| Message-ID: | 5ede3d20-b641-1cc9-120c-12bf0d8e6d07@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 9/13/17 09:25, Alvaro Herrera wrote:
> Tom Lane wrote:
>> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>
>>> I suspect this is an opportunity for documentation enhancement as opposed
>>> to a bug.
>>
>> The reason appears to be that the dependency setup for a sequence created
>> to support IDENTITY is randomly different from that for a serial sequence.
>> I'm not sure this is a good thing.
>
> It would be bad to break queries all over the internet that assume that
> sequences for columns can be found using pg_get_serial_sequence, so I
> agree this should be fixed.
Proposed patch attached.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Apply-pg_get_serial_sequence-to-identity-column-sequ.patch | text/plain | 7.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-09-14 21:45:55 | Re: BUG #14808: V10-beta4, backend abort |
| Previous Message | Thomas Munro | 2017-09-14 21:10:25 | Re: BUG #14808: V10-beta4, backend abort |