Re: Shouldn't CREATE TABLE LIKE copy the relhasoids property?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Shouldn't CREATE TABLE LIKE copy the relhasoids property?
Date: 2015-04-20 16:17:01
Message-ID: CA+TgmobJt_20JzHEeuV42v02efm5d8DaP-RPahhFdjhgANG0cQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 9, 2015 at 5:33 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Thu, Apr 9, 2015 at 12:32:23PM -0300, Alvaro Herrera wrote:
>> Bruce Momjian wrote:
>>
>> > Should this be listed in the release notes as a backward-incompatibility?
>>
>> Isn't this a backpatchable bug fix?
>
> Uh, I don't think so. I think users are used to the existing behavior
> and changing it on them will cause more harm than good. Also, we have
> had zero field reports about this problem.

I agree. This should not be back-patched, but fixing it in master seems fine.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-04-20 16:22:56 Re: Sequence Access Method WIP
Previous Message Robert Haas 2015-04-20 16:15:45 Re: Clock sweep not caching enough B-Tree leaf pages?