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

From Peter Eisentraut
Subject Re: Tables created WITH OIDS cannot be dumped/restored properly
Date
Msg-id abbb973b-1d5c-520e-2e78-b52a682286a5@2ndquadrant.com
Whole thread Raw
In response to Tables created WITH OIDS cannot be dumped/restored properly  (Derek Nelson <derek@pipelinedb.com>)
Responses Re: Tables created WITH OIDS cannot be dumped/restored properly  (Derek Nelson <derek@pipelinedb.com>)
List pgsql-bugs
On 01/11/2018 20:56, Derek Nelson wrote:
> Hello PG community! I'm one of the PipelineDB developers (PostgreSQL 
> extension) and as we've begun adding support for PG 11 our test 
> infrastructure identified an issue with dumping/restoring tables created 
> WITH OIDs. Naturally this also affects pg_upgrade.
> 
> If a table is created WITH OIDS, dumped and then restored, the resulting 
> table will not contain the OID column.

Good catch.  It's actually only if the affected table is the first table
in the output (or perhaps some other narrow circumstances).  We do have
a test case for WITH OIDS tables, but that table ends up not the first
in the output.

I propose to apply the attached patch.  It's slightly different from
yours in that I don't think we need to change the type of the withOids
field.

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

Attachment

pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: BUG #15449: file_fdw using program cause exit code error whenusing LIMIT
Next
From: Etsuro Fujita
Date:
Subject: Re: BUG #15449: file_fdw using program cause exit code error whenusing LIMIT