Re: Multiple tables row insertions from single psql input file

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Multiple tables row insertions from single psql input file
Date: 2024-06-11 04:40:11
Message-ID: CANzqJaDkSP3=gr7FGxBCHmG6g9hfx=sDha0M52RK8hxRm911+A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jun 10, 2024 at 5:16 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Mon, Jun 10, 2024 at 12:43 PM Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
>> wrote:
>
>
>> Most useful to you will be some number of "ALTER TABLE <foo> DISABLE
>> TRIGGER ALL;" statements near the beginning of the file, and their "ALTER
>> TABLE ... ENABLE TRIGGER ALL;" counterparts near the end of the file.
>>
>>
> Have you just not heard of deferred constraints or is there some reason
> besides deferring constraints that you'd want to use alter table in
> transactional production code?
>

I mentioned bulk loading of data. Occasionally that's useful, even in a
prod database.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Shenavai, Manuel 2024-06-11 06:55:03 autoanalyze / autovacuum vs manually executed "vacuum analyze"
Previous Message Kashif Zeeshan 2024-06-11 03:27:23 Re: Vacuum backend with backend_xmin?