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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "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-28 03:24:50
Message-ID: 20150428032450.GY4369@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:

> Agreed. Here is an attached patch for 9.6 which works for multiple
> LIKE'ed tables with multiple inheritance and index creation. I figured
> out why Tom's OID primary key test was failing so I now process the
> columns and LIKE first, then the constraints. There is also no longer a
> dependency on default_with_oids.

It seems to me that waiting for 9.6 for what's arguably a bug fix is too
much. It's not like this is a new feature. Why don't we just make sure
it is as correct as possible and get it done for 9.5? It's not even in
beta yet, nor feature freeze.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2015-04-28 03:31:25 Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Previous Message Andrew Dunstan 2015-04-28 03:06:17 Re: Allow SQL/plpgsql functions to accept record