Re: Tables created WITH OIDS cannot be dumped/restored properly

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Derek Nelson <derek(at)pipelinedb(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Tables created WITH OIDS cannot be dumped/restored properly
Date: 2018-11-20 08:33:21
Message-ID: 0cbff083-bcb1-ac87-1442-6f77095d3156@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 15/11/2018 04:27, Derek Nelson wrote:
> Thank you so much Peter! Is this backported to the official PG11
> releases or will it become available when 11.x is out?

I'm not quite sure what the difference between these two statements is.
The fix will be in PG 11.2 in any case.

By the way, we are currently planning on getting rid of WITH OIDS
support altogether in PG 12.

> On Tue, Nov 13, 2018, 12:54 AM Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com
> <mailto:peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> On 12/11/2018 21:00, Derek Nelson wrote:
> > Thanks for the quick turnaround! I considered only changing the
> type of
> > currWithOids but thought it may make sense to change both for
> uniformity
> > as well as future proofing against a similar issue being introduced
> > again moving forward. In any case, this seems like a good, minimal
> > fix--thanks again!
>
> Committed to master and PG11.
>
> --
> Peter Eisentraut              http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2018-11-20 08:53:16 Re: BUG #15356: Inconsistent documentation about CREATE TYPE
Previous Message Tom Lane 2018-11-19 22:12:53 Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT