MIME-Version: 1.0
References: <CANzqJaBF6mnUy1ZfBbySzSr1AfErnrMEGJaUvdSA1H9ZXkTbEw@mail.gmail.com>
 <20240715143518.3v5xdfuj27ryzuzh@hjp.at>
In-Reply-To: <20240715143518.3v5xdfuj27ryzuzh@hjp.at>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Mon, 15 Jul 2024 10:53:46 -0400
Message-ID: <CANzqJaCZkwRon9xDOeFaTd05KZM--Eei1SAiattJXurx_8n0bQ@mail.gmail.com>
Subject: Re: How does this FK constraint error happen?
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="00000000000026e36e061d4a66b5"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaCZkwRon9xDOeFaTd05KZM--Eei1SAiattJXurx_8n0bQ%40mail.gmail.com>
Precedence: bulk

--00000000000026e36e061d4a66b5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 15, 2024 at 10:35=E2=80=AFAM Peter J. Holzer <hjp-pgsql@hjp.at>=
 wrote:
[snip]

>
> Is it possible that some other process created an entry in
> rel_group_user between these two queries?


That was, in fact, the problem.  At just the wrong time to impact one of
the child databases (TAPd), but not the other two (TAPb and TAPc).

TAPd=3D# select * from rel_group_user
where user_id between 1100 and 1300
order by user_id;
 user_id | group_id | modified_by |       modified_on
---------+----------+-------------+-------------------------
    1133 |        2 |        1133 | 2024-07-15 08:43:35.669
    1142 |        2 |        1142 | 2024-07-15 09:05:58.451
    1147 |        2 |        1147 | 2024-07-15 09:30:37.169
    1158 |        2 |        1158 | 2024-07-15 09:36:45.142
    1197 |        2 |        1197 | 2024-07-15 09:52:58.477
    1210 |        2 |        1210 | 2024-07-15 02:42:09.355  <<<<<<<<<<<<<
    1229 |        2 |        1229 | 2024-07-15 08:33:48.443
    1242 |        2 |        1242 | 2024-07-15 10:29:51.176
    1260 |        2 |        1260 | 2024-07-15 07:36:21.182
    1283 |        2 |        1283 | 2024-07-15 09:48:25.214
    1288 |        2 |        1288 | 2024-07-15 08:10:33.609
(11 rows)

TAPd=3D# select user_id, login_id, created_on, modified_on
TAPd-# from public.access_user
TAPd-# where user_id =3D 1210;
 user_id |  login_id  |       created_on        |       modified_on
---------+------------+-------------------------+-------------------------
    1210 | JORIEUSER3 | 2023-10-20 11:54:24.562 | 2024-07-15 02:42:09.355
(1 row)

--00000000000026e36e061d4a66b5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jul 15, 2024 at 10:35=E2=80=AFAM =
Peter J. Holzer &lt;<a href=3D"mailto:hjp-pgsql@hjp.at">hjp-pgsql@hjp.at</a=
>&gt; wrote:<br></div><div class=3D"gmail_quote"><div>[snip]=C2=A0</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Is it possible that some other process created an entry in<br>
rel_group_user between these two queries?</blockquote><div>=C2=A0</div><div=
>That was, in fact, the problem.=C2=A0 At just the wrong time to impact one=
 of the child databases (TAPd), but not the other two (TAPb and TAPc).</div=
><div><br></div><font face=3D"monospace">TAPd=3D# select * from rel_group_u=
ser<br>where user_id between 1100 and 1300<br>order by user_id;<br>=C2=A0us=
er_id | group_id | modified_by | =C2=A0 =C2=A0 =C2=A0 modified_on =C2=A0 =
=C2=A0 =C2=A0 <br>---------+----------+-------------+----------------------=
---<br>=C2=A0 =C2=A0 1133 | =C2=A0 =C2=A0 =C2=A0 =C2=A02 | =C2=A0 =C2=A0 =
=C2=A0 =C2=A01133 | 2024-07-15 08:43:35.669<br>=C2=A0 =C2=A0 1142 | =C2=A0 =
=C2=A0 =C2=A0 =C2=A02 | =C2=A0 =C2=A0 =C2=A0 =C2=A01142 | 2024-07-15 09:05:=
58.451<br>=C2=A0 =C2=A0 1147 | =C2=A0 =C2=A0 =C2=A0 =C2=A02 | =C2=A0 =C2=A0=
 =C2=A0 =C2=A01147 | 2024-07-15 09:30:37.169<br>=C2=A0 =C2=A0 1158 | =C2=A0=
 =C2=A0 =C2=A0 =C2=A02 | =C2=A0 =C2=A0 =C2=A0 =C2=A01158 | 2024-07-15 09:36=
:45.142<br>=C2=A0 =C2=A0 1197 | =C2=A0 =C2=A0 =C2=A0 =C2=A02 | =C2=A0 =C2=
=A0 =C2=A0 =C2=A01197 | 2024-07-15 09:52:58.477<br>=C2=A0 =C2=A0 1210 | =C2=
=A0 =C2=A0 =C2=A0 =C2=A02 | =C2=A0 =C2=A0 =C2=A0 =C2=A01210 | 2024-07-15 02=
:42:09.355=C2=A0 &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;<br>=
=C2=A0 =C2=A0 1229 | =C2=A0 =C2=A0 =C2=A0 =C2=A02 | =C2=A0 =C2=A0 =C2=A0 =
=C2=A01229 | 2024-07-15 08:33:48.443<br>=C2=A0 =C2=A0 1242 | =C2=A0 =C2=A0 =
=C2=A0 =C2=A02 | =C2=A0 =C2=A0 =C2=A0 =C2=A01242 | 2024-07-15 10:29:51.176<=
br>=C2=A0 =C2=A0 1260 | =C2=A0 =C2=A0 =C2=A0 =C2=A02 | =C2=A0 =C2=A0 =C2=A0=
 =C2=A01260 | 2024-07-15 07:36:21.182<br>=C2=A0 =C2=A0 1283 | =C2=A0 =C2=A0=
 =C2=A0 =C2=A02 | =C2=A0 =C2=A0 =C2=A0 =C2=A01283 | 2024-07-15 09:48:25.214=
<br>=C2=A0 =C2=A0 1288 | =C2=A0 =C2=A0 =C2=A0 =C2=A02 | =C2=A0 =C2=A0 =C2=
=A0 =C2=A01288 | 2024-07-15 08:10:33.609<br>(11 rows)<br><br>TAPd=3D# selec=
t user_id, login_id, created_on, modified_on<br>TAPd-# from public.access_u=
ser<br>TAPd-# where user_id =3D 1210;<br>=C2=A0user_id | =C2=A0login_id =C2=
=A0| =C2=A0 =C2=A0 =C2=A0 created_on =C2=A0 =C2=A0 =C2=A0 =C2=A0| =C2=A0 =
=C2=A0 =C2=A0 modified_on =C2=A0 =C2=A0 =C2=A0 <br>---------+------------+-=
------------------------+-------------------------<br>=C2=A0 =C2=A0 1210 | =
JORIEUSER3 | 2023-10-20 11:54:24.562 | 2024-07-15 02:42:09.355<br>(1 row)<b=
r></font><div>=C2=A0</div></div></div>

--00000000000026e36e061d4a66b5--