[5.2.x] Fixed #36502 -- Restored UNNEST strategy for foreign key bulk inserts on PostgreSQL.

Regression in 764af7a3d6c0b543dcf659a2c327f214da768fe4.

Backport of 0fe218842e0e396e3ab3982bd21227968a9e7fd8 from main.

1 files changed, 16 insertions, 1 deletions

diff --git a/tests/backends/postgresql/test_compilation.py b/tests/backends/postgresql/test_compilation.py
index 67fe893e35..11c4015e01 100644
--- a/tests/backends/postgresql/test_compilation.py
+++ b/tests/backends/postgresql/test_compilation.py
@@ -1,10 +1,11 @@
 import unittest
+from datetime import date
 
 from django.db import connection
 from django.db.models.expressions import RawSQL
 from django.test import TestCase
 
-from ..models import Square
+from ..models import Article, Reporter, Square
 
 
 @unittest.skipUnless(connection.vendor == "postgresql", "PostgreSQL tests")
@@ -27,3 +28,17 @@ class BulkCreateUnnestTests(TestCase):
                 [Square(root=2, square=4), Square(root=3, square=9)]
             )
         self.assertIn("UNNEST", ctx[0]["sql"])
+
+    def test_unnest_eligible_foreign_keys(self):
+        reporter = Reporter.objects.create()
+        with self.assertNumQueries(1) as ctx:
+            articles = Article.objects.bulk_create(
+                [
+                    Article(pub_date=date.today(), reporter=reporter),
+                    Article(pub_date=date.today(), reporter=reporter),
+                ]
+            )
+        self.assertIn("UNNEST", ctx[0]["sql"])
+        self.assertEqual(
+            [article.reporter for article in articles], [reporter, reporter]
+        )