Re: Huge tables, trying to delete OID's taking 6+hours per table - Mailing list pgsql-general

From Tory M Blue
Subject Re: Huge tables, trying to delete OID's taking 6+hours per table
Date
Msg-id CAEaSS0YNA4XL5JkFB2H8_+FZ2LcEyCFAkRgUkoW6s6Ubxbmt3Q@mail.gmail.com
Whole thread Raw
In response to Re: Huge tables, trying to delete OID's taking 6+hours per table  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Huge tables, trying to delete OID's taking 6+hours per table  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-general


On Tue, May 19, 2020 at 6:40 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Tory M Blue <tmblue@gmail.com> writes:
> The command i'm using is
> ALTER TABLE tablename SET WITHOUT OIDS;
> Would a drop column oid be better?

Unfortunately, you're kind of stuck.  OIDs are not like regular columns
(at least before v12) --- they are integrated into the tuple header in
a hackish way, and so there's no way to get rid of them without a table
rewrite.

                        regards, tom lane

Poop :) kind of figured that, so it's just painful.

But  I guess if it's doing a table rewrite, is there any configuration params I could boost to help it? Shared_buffers, give it more, work mem, maintenance mem, temp buffers anything you can think of?

Thanks again Tom

Tory 

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: idle_in_transaction_session_timeout not getting log in PG v12.2
Next
From: Ron
Date:
Subject: Re: Huge tables, trying to delete OID's taking 6+hours per table