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>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Tables created WITH OIDS cannot be dumped/restored properly
Date: 2018-11-13 08:54:34
Message-ID: ceda84e0-7b29-2d55-14bc-c624fb3a3dc1@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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 Thomas Munro 2018-11-13 09:00:38 Re: Fail to create PK or index for large table in Windows
Previous Message Thomas Munro 2018-11-13 04:54:15 Re: BUG #15495: Ldap authentication not working with multiple server in Postgresql 11