Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wO0gD-001FIw-0P for pgsql-general@arkaria.postgresql.org; Fri, 15 May 2026 22:06:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wO0g9-001gUQ-1V for pgsql-general@arkaria.postgresql.org; Fri, 15 May 2026 22:06:45 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wNxmY-001KxD-1H for pgsql-general@lists.postgresql.org; Fri, 15 May 2026 19:01:10 +0000 Received: from mail-qv1-xf2d.google.com ([2607:f8b0:4864:20::f2d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1wNxmV-00000000ncE-3HdN for pgsql-general@postgresql.org; Fri, 15 May 2026 19:01:09 +0000 Received: by mail-qv1-xf2d.google.com with SMTP id 6a1803df08f44-8bc3ef10cc4so1653966d6.1 for ; Fri, 15 May 2026 12:01:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1778871665; cv=none; d=google.com; s=arc-20240605; b=U5gVtiPAYHoOf6DTSNk9eEXo9lZ5ylqxFDQDUNJV8vAdQXxxmjB8INJJffO3ZPGtuN nITXOykEk2fwLIxYgGtOGYu5JmV5zC2Lh4+qWukGNVHeRQ8OfMKJ6LvaJqohemIB5CN8 DInNBOxSF/oXgFIBLkedyrSwoUvptrWmNmIATWIc8pmwzpmKq3M4lw+EgsmmZasL1B5M LUus8cW4UcRl0+vi0kHgDlMFsoP36TWnBJTLJBq471de59e9343OALznNFFtsEVtU7B2 9odb4ZlhAnr+siYwSGFkUss1pBc4XxZu8Z+f1bZ9UIydJ8u8Xjwx3MPC0KwjPWurLNBY a6wg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20240605; h=to:subject:message-id:date:from:mime-version:dkim-signature; bh=6gGXqEdLCsPO/vyefmr+V4fZnUNRMOxMdmFa+Wz/n/I=; fh=x9Jmr8+FtiCQKUvo/7/je6SkcsG+V48pI/LmEXQOSec=; b=dKyvrIumXTZBs3PslqrO2ynTREQPB47pxt2q4ES1TDjYRu5kLH6vTSwoDri4FtgFVU 1dy0NWPtjI9lX8G2mbpUZCmTLQEskK0P/9nY5YEUCas7kc6Nn9Bdx0o+khk6p7MH/45/ WPTqhJo4fudDM/mupw2yIx5+uGKoOC0PxXS7TuvMVXdBakfCzFhNtZgeQVLjA2EFQSVl O1LV4WtErlwnkPosltoRle2Oo6uyKu0SvhQBuwJEgeyiiM7KB78Cf1C1nQIZLKGBi/p/ 8T6n83Mxt8bncPWK6pEateVrFN6vLYjBbqBmSz84dGdHtn2rF3NLJ9sVZvIa/9Z5b6go CiuA==; darn=postgresql.org ARC-Authentication-Results: i=1; mx.google.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1778871665; x=1779476465; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=6gGXqEdLCsPO/vyefmr+V4fZnUNRMOxMdmFa+Wz/n/I=; b=SpkHmBwBSmmItiMSNu6s6aq6LGxpFi/Rhn3YBO5EmyOXH3BEt/lN1ZJdqHvG+J3QlL TzFf8gI1HL+3IMjip4gecIbf+PS1kU8j0Xo/k4DffHf2DL4+EnHqMjof7AsgCcuxuXB6 eLS9So4jjEo/jU66evFmsRs8Kvz3JDcrEkkapW0rrh1+L2KfuBLCZrIhbsNRU3G5pFsr oEJfP4vr8BBIYN7fslpuyOPFYI0CrKqgwe4S5udcilr0WmXHm/KOg1dwzwFLhGYc52cc wUxd58DZng5AdzXvf0Zx9haoHu3ZUQeZq4b7dZk80CJEShLFG03VDhbiFx1XRs/iDZF5 4fpQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1778871665; x=1779476465; h=to:subject:message-id:date:from:mime-version:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=6gGXqEdLCsPO/vyefmr+V4fZnUNRMOxMdmFa+Wz/n/I=; b=angSeYiswc2OJW+0xSiIOH3e0xIV3rKQDDrKAEAA808KDHEMi6HfhonU25zHLTJkz6 OntsQiaIddl/pxI8JHvwh3UzljX0JXEXEC+4FcbcS/UQZ3oOXlALy7lzJQKAxxnB9LBk yAOMJxibjoilQBv/XejYUc4uXbAialEJW1dMcoZk4X9yyhj8kGAkGnxCvgTMh8ZjPndh zHXG3o6k0oFiJRox/Zoyd22bYNEDFQYwOi7Xb4vu20JGcFPTKXXtJOlsejlCf9LCVCvb mjU9hvnDfX7gdOVnLcA1xdCzBBWM+S5sCGa+kL0dGassIehiShY1KYgnec2Do2XqtwTI +clw== X-Gm-Message-State: AOJu0YyMRul+v5/aj6XiRWKBjOVPd7K1GQIicEV6E4zTosNdT03DS/hj pNW6F+pdK6FfArVAvd2s8d5qoyxlPxa2+zEZBROpAYDXlHXw3Yy7oiO6/yqSRVEDvFJ+0xd7imw cDxichYcO5bOIUcWgfxwfgZHBUhEVWwmNEA== X-Gm-Gg: Acq92OHp7ROcjek9Ph7nERHxtnTzQsnvlHYYUEV4Q5OiD6/PX4RYF1mUy/r+zlB6oER 54F4GcCAkwCahEIJ1w8JZ46OykrPieWhawl1x24KOH5jkp8j43U3FiU+mtx4srQQZBSFbG14NGx U0bNJtKi3JXTS5GAQax1vJnS2dSfVAYUTR1NylwDQwHyy/9IBeYOTclqP6X1/aKPB2QskpHTfxC UIqgXsDqKzU6PYoFfLk3/FYqY3VJP/wKGZzBV+76iRO6lmpHpMEySj4bg/75qo3OmL/ANg+lNwn 8cpa9YDevzhFMd6uRAyaSroxQNQ4xPgYFKRJoqwY470MXG55Q6kNREH++dQpdW4R6ChXNf9nynE = X-Received: by 2002:a05:6214:8082:b0:8bd:de6d:c33b with SMTP id 6a1803df08f44-8ca0f67c426mr82049446d6.24.1778871664725; Fri, 15 May 2026 12:01:04 -0700 (PDT) MIME-Version: 1.0 From: Shivam Pandey Date: Sat, 16 May 2026 00:30:52 +0530 X-Gm-Features: AVHnY4LuYAhdE8ZWCY3wvgpbU6MaE8OoSxsfFZd26Kqg2eW_A7LaOTY4_QiKooI Message-ID: Subject: Suggestion for Easier Cross-Database Query Handling in PostgreSQL To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000ad6c730651dfd58c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ad6c730651dfd58c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello PostgreSQL Team, I would like to share feedback from a developer perspective regarding cross-database querying in PostgreSQL. One feature that many developers appreciate in MySQL is the ability to directly query and join tables across multiple databases within the same server instance. This approach becomes very useful in real-world situations where applications need to access shared or distributed data quickly and efficiently. In PostgreSQL, achieving similar functionality often requires additional setup using extensions such as postgres_fdw or dblink. While these solutions are powerful and architecturally clean, they can feel complex for developers who are building applications rapidly or migrating from systems like MySQL. It would be valuable if PostgreSQL could provide a more developer-friendly and simplified native approach for cross-database querying while still maintaining PostgreSQL=E2=80=99s strong isolation and security principles. Possible improvements could include: 1)Simpler syntax for cross-database joins 2) Easier configuration for trusted local databases 3) Built-in lightweight federation support 4) Better onboarding documentation for multi-database use cases PostgreSQL is already one of the most powerful and respected databases in the industry. Enhancing developer convenience in this area could make adoption even smoother for many teams. Thank you for your incredible work and continuous innovation. Best Regards, Shivam Pandey --000000000000ad6c730651dfd58c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello PostgreSQL Team,

I would like to share feedback from a developer perspective rega= rding cross-database querying in PostgreSQL.

One feature that many developers appreciate in MySQL i= s the ability to directly query and join tables across multiple databases w= ithin the same server instance. This approach becomes very useful in real-w= orld situations where applications need to access shared or distributed dat= a quickly and efficiently.

In PostgreSQL, achieving similar functionality often requires additional= setup using extensions such as postgres_fdw or dblink. While these solutio= ns are powerful and architecturally clean, they can feel complex for develo= pers who are building applications rapidly or migrating from systems like M= ySQL.

It would be valuab= le if PostgreSQL could provide a more developer-friendly and simplified nat= ive approach for cross-database querying while still maintaining PostgreSQL= =E2=80=99s strong isolation and security principles.

Possible improvements could include:

1)Simpler syntax for cross-databa= se joins
2) Easier configuration for trusted local d= atabases
3) Built-in lightweight federation support<= /div>
4) Better onboarding documentation for multi-databas= e use cases

PostgreSQL i= s already one of the most powerful and respected databases in the industry.= Enhancing developer convenience in this area could make adoption even smoo= ther for many teams.

Tha= nk you for your incredible work and continuous innovation.

Best Regards,
Shi= vam Pandey=C2=A0
--000000000000ad6c730651dfd58c--