Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Manuel Rigger <rigger(dot)manuel(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: ALTER TABLE SET WITH OIDS fails after failed CONCURRENTLY index creation
Date: 2019-07-08 06:01:18
Message-ID: 20190708060118.GC2709@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sat, Jul 06, 2019 at 01:36:21AM +0200, Manuel Rigger wrote:
> Okay, thanks for the explanation and sorry for the false alarm!

Another thing which you may be interested in is that support for SET
WITH OIDS has been dropped as of v12.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ádám Maracska 2019-07-08 07:45:00 PostgreSQL 11 can not restart after an unexpected shutdown
Previous Message Tom Lane 2019-07-08 01:10:27 Re: Issue with CHAR column and "column LIKE column" condition