From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Copying records from TABLE_A to TABLE_B (in the same database) |
Date: | 2022-08-02 19:01:46 |
Message-ID: | f9165084-d475-8023-2d4e-6dc3a7459b00@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 8/2/22 13:51, Thomas Kellerer wrote:
> Ron schrieb am 02.08.2022 um 20:37:
>> AWS RDS Postgresql 12.10
>>
>> There are no indices or constraints (except for NOT NULL) on table_a.
>>
>> The two ways that I know are:
>> INSERT INTO table_a SELECT * FROM table_b;
>> and
>> \COPY table_a TO '/tmp/table_a.tsv' WITH (FORMAT BINARY);
>> \COPY table_b FROM '/tmp/table_a.tsv' WITH (FORMAT BINARY);
>>
>> Is there a faster/better way?
>
> The INSERT is most probably faster then \copy
That's what I figured, since COPY means moving data over the (admittedly
very fast) wire, onto disk, and then back over the wire into the new table.
>
> Another option is to have a trigger on table_a
> to automatically replay all DML on table_b
How would you originally populate it?
> Logical replication might be another option.
> Although I am not sure if that is even possible inside
> the samme database.
> I know it's tricky inside the same server
> (between different databases)
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2022-08-02 19:02:35 | Re: Copying records from TABLE_A to TABLE_B (in the same database) |
Previous Message | Rob Sargent | 2022-08-02 18:59:36 | Re: Copying records from TABLE_A to TABLE_B (in the same database) |