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.94.2) (envelope-from ) id 1txAmL-0046vH-ER for pgsql-general@arkaria.postgresql.org; Tue, 25 Mar 2025 20:21:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1txAmJ-009Qky-Ti for pgsql-general@arkaria.postgresql.org; Tue, 25 Mar 2025 20:21:39 +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.94.2) (envelope-from ) id 1txAmJ-009Qkh-IX for pgsql-general@lists.postgresql.org; Tue, 25 Mar 2025 20:21:39 +0000 Received: from sm-r-010-dus.org-dns.com ([84.19.1.238]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1txAmH-00196C-0L for pgsql-general@lists.postgresql.org; Tue, 25 Mar 2025 20:21:39 +0000 Received: from smarthost-dus.org-dns.com (localhost [127.0.0.1]) by smarthost-dus.org-dns.com (Postfix) with ESMTP id 1EA9DA0278 for ; Tue, 25 Mar 2025 21:21:36 +0100 (CET) Received: by smarthost-dus.org-dns.com (Postfix, from userid 1001) id 1220BA048D; Tue, 25 Mar 2025 21:21:36 +0100 (CET) X-Spam-Status: No, score=-0.9 required=5.0 tests=AWL,BAYES_00,KAM_INFOUSMEBIZ, SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=3.4.6 Received: from ha01s018.org-dns.com (ha01s018.org-dns.com [62.108.32.138]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smarthost-dus.org-dns.com (Postfix) with ESMTPS id D1913A0278 for ; Tue, 25 Mar 2025 21:21:35 +0100 (CET) Authentication-Results: ha01s018.org-dns.com; spf=pass (sender IP is 146.185.68.202) smtp.mailfrom=thiemo@gelassene-pferde.biz smtp.helo=[192.168.178.23] Received-SPF: pass (ha01s018.org-dns.com: connection is authenticated) Message-ID: <8a694e38-e10c-4ce8-8d4c-8ac0bd8f1b75@gelassene-pferde.biz> Date: Tue, 25 Mar 2025 21:21:34 +0100 MIME-Version: 1.0 Subject: Re: How to pass a list of locations (longitude, latitude) to a PostgreSQL/PostGIS stored function? To: pgsql-general@lists.postgresql.org References: <1284143.1742922449@sss.pgh.pa.us> Content-Language: de-CH-frami, en-GB, it-CH, fr-CH, es-CL, es-ES From: Thiemo Kellner In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-PPP-Message-ID: <174293409564.873582.16434795732714331208@ha01s018.org-dns.com> X-PPP-Vhost: gelassene-pferde.biz X-POWERED-BY: wint.global - AV:CLEAN SPAM:OK List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk El 25-03-25 a las 18:58, Christoph Berg escribió: > Re: Tom Lane >> You might be best advised to create a composite >> type like "location (long bigint, lat bigint)" and use an array of >> that. > Or use the geometry types from PostGIS, since you are probably going > to do geo lookups on these points anyway. > > Christoph Why is pure SQL not an option instead of a procedure/function?