On Sun, Feb 4, 2024 at 12:50 AM Francisco Olarte
wrote:
> On Sat, 3 Feb 2024 at 19:29, Greg Sabino Mullane
> wrote:
> ...
> > Given the size of your table, you probably want to divide that up.
> > As long as nothing is changing the original table, you could do:
> >
> > insert into mytable2
On 2024-02-03 19:25:12 +0530, Lok P wrote:
> Apology. One correction, the query is like below. I. E filter will be on on
> ctid which I believe is equivalent of rowid in oracle and we will not need the
> index on Id column then.
>
> But, it still runs long, so thinking any other way to make the
On Sat, 3 Feb 2024 at 19:29, Greg Sabino Mullane wrote:
...
> Given the size of your table, you probably want to divide that up.
> As long as nothing is changing the original table, you could do:
>
> insert into mytable2 select * from mytable1 order by ctid limit 10_000_000
> offset 0;
> insert
As a general rule, avoid heavy subselects like that. You don't need to
build a full list of duplicates before starting. Another approach:
create table mytable2 (like mytable1);
alter table mytable2 add primary key (id);
insert into mytable2 select * from mytable1 on conflict do nothing;
Given
Ron Johnson
7:37 PM (1 hour ago)
to *pgsql-general*
On Sat, Feb 3, 2024 at 7:37 PM Ron Johnson wrote:
> On Sat, Feb 3, 2024 at 8:55 AM Lok P wrote:
>
>> Apology. One correction, the query is like below. I. E filter will be on
>> on ctid which I believe is equivalent of rowid in oracle and we
On Sat, Feb 3, 2024 at 8:55 AM Lok P wrote:
> Apology. One correction, the query is like below. I. E filter will be on
> on ctid which I believe is equivalent of rowid in oracle and we will not
> need the index on Id column then.
>
> But, it still runs long, so thinking any other way to make
I copy/pasted your question into ChatGPT, and it gave me 10 specific
suggestions. Have you tried those?
On Sat, Feb 3, 2024 at 10:55 AM Lok P wrote:
> Apology. One correction, the query is like below. I. E filter will be on
> on ctid which I believe is equivalent of rowid in oracle and we will
Apology. One correction, the query is like below. I. E filter will be on on
ctid which I believe is equivalent of rowid in oracle and we will not need
the index on Id column then.
But, it still runs long, so thinking any other way to make the duplicate
removal faster?
Also wondering , the index
Hello All,
A non partitioned table having ~4.8 billion rows in it and having data size
as ~1.4TB , row size as ~313 bytes having ~127 columns in it. This has got
approx ~1billion+ duplicate rows inserted in it and we want to get the
duplicate data removed for this table and create a PK/unique
