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 1tHZQt-008W4E-Vx for pgsql-general@arkaria.postgresql.org; Sun, 01 Dec 2024 02:11:36 +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 1tHZQp-003fll-Rl for pgsql-general@arkaria.postgresql.org; Sun, 01 Dec 2024 02:11:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tHZQp-003fdH-F8 for pgsql-general@lists.postgresql.org; Sun, 01 Dec 2024 02:11:32 +0000 Received: from mout-p-102.mailbox.org ([80.241.56.152]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tHZQm-000PZw-Cs for pgsql-general@postgresql.org; Sun, 01 Dec 2024 02:11:30 +0000 Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4Y19Q26Ff0z9sdP; Sun, 1 Dec 2024 03:11:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailbox.org; s=mail20150812; t=1733019082; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=5AQsPE+azdRHg4iRwr1Vu9sxf8FmOsPZ5MoSunVMNPY=; b=Jm6a8KLQWj0ce3hf4nhbT0kpASzKYmbLRt1tfItR2AF9M5nRMm+fE7nPtl70GDLJPS4Xyz 7LcvkCEBqkz1/D+TuZgL0pBcfSk1+BS0J6lWyMAuvrgXkjt1s/ykSjRhxwhB6KcuSKJWOt TKUOeN3BQ5AQKXlemIkH+4cMZLbz+p/SU3N5bbqIkHPOcOdh1T6Sdqw4L0E3iUvBnUm/KG IzntxuuolQYKAIMzeGQ3Y4kTnFvZLfcBjAzTfrM5uPgQqauzsy9XfZ8NrSKJNWNE3bWh/z ytMKylJ9kPOLkJGQUgJtYzFUqKMzGq686Db4saYEq+ASyw4n7MyvdTvda3EfAw== Content-Type: multipart/alternative; boundary="------------quYyZokvUojvZRzb6NV4Mypb" Message-ID: Date: Sat, 30 Nov 2024 18:11:18 -0800 MIME-Version: 1.0 Subject: Re: Errors when restoring backup created by pg_dumpall To: "David G. Johnston" Cc: Adrian Klaver , "pgsql-general@postgresql.org" References: <6a6439f1-8039-44e2-8fb9-59028f7f2014@mailbox.org> <9c5ba566-27b8-4e8c-bf7d-2dc561509991@mailbox.org> Content-Language: en-US From: PopeRigby In-Reply-To: X-MBO-RS-META: 91pbfc63tw8j5smmxru8h4ks6trzrmgb X-MBO-RS-ID: 20e8aa369f3e6444b05 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------quYyZokvUojvZRzb6NV4Mypb Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 11/30/24 17:27, David G. Johnston wrote: > On Saturday, November 30, 2024, PopeRigby wrote: > > On 11/29/24 17:47, Adrian Klaver wrote: > > On 11/29/24 17:34, PopeRigby wrote: > > psql:all.sql:4104: ERROR:  type "earth" does not exist > LINE 1: > ...ians($1))*sin(radians($2))),earth()*sin(radians($1)))::earth > > QUERY:  SELECT > cube(cube(cube(earth()*cos(radians($1))*cos(radians($2))),earth()*cos(radians($1))*sin(radians($2))),earth()*sin(radians($1)))::earth > CONTEXT:  SQL function "ll_to_earth" during inlining >  The earthdistance module is even getting added between the > table with the earth type is added, so shouldn't there be no > problem? > > > The fact that “earth” is not schema qualified leads me to suspect you > are getting bit by safe search_path environment rules. > > David J. Ah. How can I fix that? --------------quYyZokvUojvZRzb6NV4Mypb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 11/30/24 17:27, David G. Johnston wrote:
On Saturday, November 30, 2024, PopeRigby <poperigby@mailbox.org> wrote:
On 11/29/24 17:47, Adrian Klaver wrote:
On 11/29/24 17:34, PopeRigby wrote:

psql:all.sql:4104: ERROR:  type "earth" does not exist
LINE 1: ...ians($1))*sin(radians($2))),earth()*sin(radians($1)))::earth

QUERY:  SELECT cube(cube(cube(earth()*cos(radians($1))*cos(radians($2))),earth()*cos(radians($1))*sin(radians($2))),earth()*sin(radians($1)))::earth
CONTEXT:  SQL function "ll_to_earth" during inlining
 The earthdistance module is even getting added between the table with the earth type is added, so shouldn't there be no problem?

The fact that “earth” is not schema qualified leads me to suspect you are getting bit by safe search_path environment rules.

David J. 

Ah. How can I fix that?

--------------quYyZokvUojvZRzb6NV4Mypb--