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-09 08:26:53
Message-ID: abbb973b-1d5c-520e-2e78-b52a682286a5@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
0001-pg_dump-Fix-dumping-of-WITH-OIDS-tables.patch text/plain 1.4 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Etsuro Fujita 2018-11-09 09:27:09 Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT
Previous Message Thomas Munro 2018-11-09 07:32:54 Re: BUG #15449: file_fdw using program cause exit code error when using LIMIT