pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Deferrable FK not behaving as expected.
Date: Mon, 7 Dec 2020 12:30:48 -0600
Message-ID: <3c32cc9c-1589-7f22-b9e3-f4bcccbaf87e@gmail.com> (raw)
In-Reply-To: <b97cbd9d-1615-c9e1-aff1-683a37fedee9@gmx.net>
References: <75fe0761-a291-86a9-c8d8-4906da077469@gmail.com>
	<b97cbd9d-1615-c9e1-aff1-683a37fedee9@gmx.net>

On 12/7/20 12:19 PM, Thomas Kellerer wrote:
> Ron schrieb am 07.12.2020 um 19:15:
>> Referenced by:
>>      TABLE "sales_detail" CONSTRAINT "fk_sales_detail_sales_header"
>>            FOREIGN KEY (cust_id, order_ts) REFERENCES 
>> sales_header(cust_id, order_ts) *DEFERRABLE*
>
> I think if you only mention "deferrable" this is the same as "deferrable 
> initially immediate",
> so you will need to make them deferrable in your transaction:
>
>     SET CONSTRAINTS ALL DEFERRED;
>
> or create the constraint with
>
>     deferrable initially deferred

Neither technique worked.

test=# ALTER TABLE sales_detail ALTER CONSTRAINT 
fk_sales_detail_sales_header DEFERRABLE INITIALLY DEFERRED;
ALTER TABLE

test=# \d sales_detail
                    Partitioned table "public.sales_detail"
     Column    |            Type             | Collation | Nullable | Default
--------------+-----------------------------+-----------+----------+---------
  cust_id      | integer                     |           | not null |
  order_ts     | timestamp without time zone |           | not null |
  seq_no       | integer                     |           | not null |
  inventory_id | integer                     | |          |
  quantity     | numeric(10,2)               | |          |
  price        | numeric(10,2)               | |          |
  tax_rate     | numeric(3,3)                | |          |
Partition key: RANGE (order_ts)
Indexes:
     "sales_detail_pkey" PRIMARY KEY, btree (cust_id, order_ts, seq_no)
Foreign-key constraints:
     "fk_sales_detail_sales_header" FOREIGN KEY (cust_id, order_ts)
           REFERENCES sales_header(cust_id, order_ts) *DEFERRABLE INITIALLY 
DEFERRED*
Number of partitions: 12 (Use \d+ to list them.)

test=# begin transaction;
BEGIN
test=# delete from sales_header where cust_id = 1;
ERROR:  update or delete on table "sales_header_202001" violates foreign key 
constraint "sales_detail_cust_id_order_ts_fkey" on table "sales_detail"
DETAIL:  Key (cust_id, order_ts)=(1, 2020-01-05 13:05:42.567) is still 
referenced from table "sales_detail".
test=# rollback;
ROLLBACK



-- 
Angular momentum makes the world go 'round.

view thread (10+ messages)  latest in thread

Message-ID: <3c32cc9c-1589-7f22-b9e3-f4bcccbaf87e@gmail.com>
Permalink:  ../3c32cc9c-1589-7f22-b9e3-f4bcccbaf87e@gmail.com/
Also on:    postgresql.org/message-id/3c32cc9c-1589-7f22-b9e3-f4bcccbaf87e@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: Deferrable FK not behaving as expected.
  In-Reply-To: <3c32cc9c-1589-7f22-b9e3-f4bcccbaf87e@gmail.com>
  References: <75fe0761-a291-86a9-c8d8-4906da077469@gmail.com> <b97cbd9d-1615-c9e1-aff1-683a37fedee9@gmx.net> <3c32cc9c-1589-7f22-b9e3-f4bcccbaf87e@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox