Search Postgresql Archives

Re: TRUNCATE ONLY with foreign keys and triggers disabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: TRUNCATE ONLY with foreign keys and triggers disabled
From: Laurenz Albe <laurenz.albe@xxxxxxxxxxx>
Date: Mon, 14 Apr 2025 17:07:58 +0200
Cc: pgsql-general@xxxxxxxxxxxxxxxxxxxx
In-reply-to: <c691b848-7649-e425-b066-c1116147de55@gmx.net>
References: <edf978ea-6cf8-b2c1-4866-3fa7ae160836@gmx.net> <1257959.1744641901@sss.pgh.pa.us> <e5909bae-6782-9c61-fb86-cdf3398e3c9f@gmx.net> <c691b848-7649-e425-b066-c1116147de55@gmx.net>
User-agent: Evolution 3.54.3 (3.54.3-1.fc41)

On Mon, 2025-04-14 at 17:05 +0200, Dimitrios Apostolou wrote:
> I meant the *referencing* table has just been 
> populated. I'm trying to delete the *referenced* table and I get the 
> error.

That would break the foreign key constraint, right?
PostgreSQL cannot allow that.

Yours,
Laurenz Albe

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: TRUNCATE ONLY with foreign keys and triggers disabled
  - From: Adrian Klaver

References:
- TRUNCATE ONLY with foreign keys and triggers disabled
  - From: Dimitrios Apostolou
- Re: TRUNCATE ONLY with foreign keys and triggers disabled
  - From: Tom Lane
- Re: TRUNCATE ONLY with foreign keys and triggers disabled
  - From: Dimitrios Apostolou
- Re: TRUNCATE ONLY with foreign keys and triggers disabled
  - From: Dimitrios Apostolou

Prev by Date: Re: TRUNCATE ONLY with foreign keys and triggers disabled
Next by Date: Re: TRUNCATE ONLY with foreign keys and triggers disabled
Previous by thread: Re: TRUNCATE ONLY with foreign keys and triggers disabled
Next by thread: Re: TRUNCATE ONLY with foreign keys and triggers disabled
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]