Re: Tables created WITH OIDS cannot be dumped/restored properly - Mailing list pgsql-bugs

From Derek Nelson
Subject Re: Tables created WITH OIDS cannot be dumped/restored properly
Date
Msg-id CAPjXXmgbTMdyjV=1kebYcdRvEowmODVrdsoOUkfq0fYKNPDqJQ@mail.gmail.com
Whole thread Raw
In response to Re: Tables created WITH OIDS cannot be dumped/restored properly  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Tables created WITH OIDS cannot be dumped/restored properly
List 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.eisentraut@2ndquadrant.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

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15507: undefined symbol: geod_polygon_init
Next
From: PG Bug reporting form
Date:
Subject: BUG #15508: Not able to connect irrespective of valid entries inpg_hba.conf