From: | Tory M Blue <tmblue(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Huge tables, trying to delete OID's taking 6+hours per table |
Date: | 2020-05-19 16:51:29 |
Message-ID: | CAEaSS0YNA4XL5JkFB2H8_+FZ2LcEyCFAkRgUkoW6s6Ubxbmt3Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, May 19, 2020 at 6:40 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Tory M Blue <tmblue(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2020-05-19 17:06:38 | Re: Huge tables, trying to delete OID's taking 6+hours per table |
Previous Message | Adrian Klaver | 2020-05-19 15:29:18 | Re: idle_in_transaction_session_timeout not getting log in PG v12.2 |