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

From: Derek Nelson <derek(at)pipelinedb(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Tables created WITH OIDS cannot be dumped/restored properly
Date: 2018-11-15 03:27:39
Message-ID: CAPjXXmgbTMdyjV=1kebYcdRvEowmODVrdsoOUkfq0fYKNPDqJQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thank you so much Peter! Is this backported to the official PG11 releases
or will it become available when 11.x is out?

On Tue, Nov 13, 2018, 12:54 AM Peter Eisentraut <
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
>

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2018-11-15 07:03:29 BUG #15508: Not able to connect irrespective of valid entries in pg_hba.conf
Previous Message PG Bug reporting form 2018-11-15 03:24:36 BUG #15507: undefined symbol: geod_polygon_init