On 12/13/24 08:46, Adrian Klaver wrote:
On 12/12/24 22:19, PopeRigby wrote:
On 12/10/24 21:22, Adrian Klaver wrote:
On 12/10/24 19:05, PopeRigby wrote:
If I am following correctly I believe you need this one:
https://www.postgresql.org/message-id/attachment/166859/v2-0002-Use-new-style-SQL
On 12/12/24 22:19, PopeRigby wrote:
On 12/10/24 21:22, Adrian Klaver wrote:
On 12/10/24 19:05, PopeRigby wrote:
If I am following correctly I believe you need this one:
https://www.postgresql.org/message-id/attachment/166859/v2-0002-Use-new-style-SQL-function-in-earthdistance-exten.patch
I
On 12/10/24 21:22, Adrian Klaver wrote:
On 12/10/24 19:05, PopeRigby wrote:
On 12/9/24 16:31, Adrian Klaver wrote:
On 12/9/24 15:30, PopeRigby wrote:
On 12/9/24 15:23, Tom Lane wrote:
Adrian Klaver writes:
You could file an issue here:
https://www.postgresql.org/account/login/?next=/account
On 12/10/24 19:05, PopeRigby wrote:
On 12/9/24 16:31, Adrian Klaver wrote:
On 12/9/24 15:30, PopeRigby wrote:
On 12/9/24 15:23, Tom Lane wrote:
Adrian Klaver writes:
You could file an issue here:
https://www.postgresql.org/account/login/?next=/account/submitbug/
Ask if the developers could u
On 12/9/24 16:31, Adrian Klaver wrote:
On 12/9/24 15:30, PopeRigby wrote:
On 12/9/24 15:23, Tom Lane wrote:
Adrian Klaver writes:
You could file an issue here:
https://www.postgresql.org/account/login/?next=/account/submitbug/
Ask if the developers could use the mechanisms available here:
htt
On 12/9/24 20:54, Ron Johnson wrote:
On Mon, Dec 9, 2024 at 11:24 PM David G. Johnston
mailto:david.g.johns...@gmail.com>> wrote:
On Monday, December 9, 2024, Ron Johnson mailto:ronljohnso...@gmail.com>> wrote:
On Sat, Nov 30, 2024 at 10:36 PM Adrian Klaver
mailto:adrian.kl
On Mon, Dec 9, 2024 at 11:24 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Monday, December 9, 2024, Ron Johnson wrote:
>
>> On Sat, Nov 30, 2024 at 10:36 PM Adrian Klaver
>> wrote:
>> [snip]
>>
>>> In future schema qualify all references.
>>>
>>> For now in the dump file you co
On Monday, December 9, 2024, Ron Johnson wrote:
> On Sat, Nov 30, 2024 at 10:36 PM Adrian Klaver
> wrote:
> [snip]
>
>> In future schema qualify all references.
>>
>> For now in the dump file you could search for
>>
>> SELECT pg_catalog.set_config('search_path', '', false);
>>
>> and set to
>>
>
On Sat, Nov 30, 2024 at 10:36 PM Adrian Klaver
wrote:
[snip]
> In future schema qualify all references.
>
> For now in the dump file you could search for
>
> SELECT pg_catalog.set_config('search_path', '', false);
>
> and set to
>
> SELECT pg_catalog.set_config('search_path', 'public', false);
>
On 12/9/24 15:30, PopeRigby wrote:
On 12/9/24 15:23, Tom Lane wrote:
Adrian Klaver writes:
You could file an issue here:
https://www.postgresql.org/account/login/?next=/account/submitbug/
Ask if the developers could use the mechanisms available here:
https://www.postgresql.org/docs/current/ext
On 12/9/24 15:23, Tom Lane wrote:
Adrian Klaver writes:
You could file an issue here:
https://www.postgresql.org/account/login/?next=/account/submitbug/
Ask if the developers could use the mechanisms available here:
https://www.postgresql.org/docs/current/extend-extensions.html#EXTEND-EXTENSION
On 12/9/24 15:23, Tom Lane wrote:
Adrian Klaver writes:
You could file an issue here:
https://www.postgresql.org/account/login/?next=/account/submitbug/
Ask if the developers could use the mechanisms available here:
https://www.postgresql.org/docs/current/extend-extensions.html#EXTEND-EXTENSION
Adrian Klaver writes:
> You could file an issue here:
> https://www.postgresql.org/account/login/?next=/account/submitbug/
> Ask if the developers could use the mechanisms available here:
> https://www.postgresql.org/docs/current/extend-extensions.html#EXTEND-EXTENSIONS-RELOCATION
This wouldn't r
On 12/9/24 14:47, Adrian Klaver wrote:
On 12/9/24 14:14, PopeRigby wrote:
On 12/7/24 11:58, David G. Johnston wrote:
On Sat, Dec 7, 2024 at 12:25 PM PopeRigby
wrote:
It actually looks like setting those all to have public fixed
all the
errors, including the one with lldap. So, how
On 12/9/24 14:14, PopeRigby wrote:
On 12/7/24 11:58, David G. Johnston wrote:
On Sat, Dec 7, 2024 at 12:25 PM PopeRigby wrote:
It actually looks like setting those all to have public fixed all the
errors, including the one with lldap. So, how can I get it to not put
public there a
On 12/9/24 14:31, David G. Johnston wrote:
On Mon, Dec 9, 2024 at 3:14 PM PopeRigby wrote:
On 12/7/24 11:58, David G. Johnston wrote:
On Sat, Dec 7, 2024 at 12:25 PM PopeRigby
wrote:
It actually looks like setting those all to have public fixed
all the
er
On Mon, Dec 9, 2024 at 3:14 PM PopeRigby wrote:
> On 12/7/24 11:58, David G. Johnston wrote:
>
> On Sat, Dec 7, 2024 at 12:25 PM PopeRigby wrote:
>
>>
>> It actually looks like setting those all to have public fixed all the
>> errors, including the one with lldap. So, how can I get it to not put
On 12/7/24 11:58, David G. Johnston wrote:
On Sat, Dec 7, 2024 at 12:25 PM PopeRigby wrote:
It actually looks like setting those all to have public fixed all the
errors, including the one with lldap. So, how can I get it to not put
public there automatically for next time?
I assu
On Sat, Dec 7, 2024 at 12:25 PM PopeRigby wrote:
>
> It actually looks like setting those all to have public fixed all the
> errors, including the one with lldap. So, how can I get it to not put
> public there automatically for next time?
>
>
I assume you mean "get it to put public there" (i.e.,
On 12/5/24 14:48, Adrian Klaver wrote:
On 12/5/24 14:32, PopeRigby wrote:
On 12/1/24 13:55, Tom Lane wrote:
Adrian Klaver writes:
On 12/1/24 13:14, Tom Lane wrote:
It would be useful to know what is the command at line 4102
of all.sql.
It is here:
https://gist.github.com/poperigby/fcb59eb6c
On Thursday, December 5, 2024, Ron Johnson wrote:
> On Thu, Dec 5, 2024 at 6:24 PM David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
>> On Thu, Dec 5, 2024 at 4:04 PM Ron Johnson
>> wrote:
>>
>>> Another alternative is to open the .sql file in Notepad++, then add
>>> "public." before al
On 12/5/24 18:44, Ron Johnson wrote:
On Thu, Dec 5, 2024 at 6:24 PM David G. Johnston
mailto:david.g.johns...@gmail.com>> wrote:
On Thu, Dec 5, 2024 at 4:04 PM Ron Johnson mailto:ronljohnso...@gmail.com>> wrote:
Another alternative is to open the .sql file in Notepad++, then
On Thu, Dec 5, 2024 at 6:24 PM David G. Johnston
wrote:
> On Thu, Dec 5, 2024 at 4:04 PM Ron Johnson
> wrote:
>
>> Another alternative is to open the .sql file in Notepad++, then add
>> "public." before all the unqualified "earth" and "ll_to_earth" references.
>>
>
> And as discussed there are n
On Thu, Dec 5, 2024 at 4:04 PM Ron Johnson wrote:
> Another alternative is to open the .sql file in Notepad++, then add
> "public." before all the unqualified "earth" and "ll_to_earth" references.
>
And as discussed there are none in that file because those references are
within an extension's o
On Thu, Dec 5, 2024 at 5:32 PM PopeRigby wrote:
> On 12/1/24 13:55, Tom Lane wrote:
> > Adrian Klaver writes:
> >> On 12/1/24 13:14, Tom Lane wrote:
> >>> It would be useful to know what is the command at line 4102
> >>> of all.sql.
> >> It is here:
> >> https://gist.github.com/poperigby/fcb59eb
On 12/5/24 14:32, PopeRigby wrote:
On 12/1/24 13:55, Tom Lane wrote:
Adrian Klaver writes:
On 12/1/24 13:14, Tom Lane wrote:
It would be useful to know what is the command at line 4102
of all.sql.
It is here:
https://gist.github.com/poperigby/fcb59eb6c22c6051800e06a0ec482b49
CREATE TABLE pub
On 12/1/24 13:55, Tom Lane wrote:
Adrian Klaver writes:
On 12/1/24 13:14, Tom Lane wrote:
It would be useful to know what is the command at line 4102
of all.sql.
It is here:
https://gist.github.com/poperigby/fcb59eb6c22c6051800e06a0ec482b49
CREATE TABLE public.geodata_places (
id intege
On 12/2/24 17:17, Tom Lane wrote:
PopeRigby writes:
On 12/1/24 12:15, Tom Lane wrote:
Cool. You did actually install the new scripts into your target
installation, right?
Oh, is applying the patch and rebuilding PostgreSQL not enough?
Not unless you did "make install" in the contrib/earthdi
PopeRigby writes:
> On 12/1/24 12:15, Tom Lane wrote:
>> Cool. You did actually install the new scripts into your target
>> installation, right?
> Oh, is applying the patch and rebuilding PostgreSQL not enough?
Not unless you did "make install" in the contrib/earthdistance
directory (or somethi
On 12/1/24 12:15, Tom Lane wrote:
Cool. You did actually install the new scripts into your target
installation, right?
Oh, is applying the patch and rebuilding PostgreSQL not enough?
Adrian Klaver writes:
> On 12/1/24 13:14, Tom Lane wrote:
>> It would be useful to know what is the command at line 4102
>> of all.sql.
> It is here:
> https://gist.github.com/poperigby/fcb59eb6c22c6051800e06a0ec482b49
> CREATE TABLE public.geodata_places (
> id integer NOT NULL,
> na
On 12/1/24 13:14, Tom Lane wrote:
Adrian Klaver writes:
On 12/1/24 12:05, PopeRigby wrote:
I'm still getting this error:
psql:all.sql:4102: ERROR: type "earth" does not exist
LINE 1: ...ians($1))*sin(radians($2))),earth()*sin(radians($1)))::earth
The issue is still this:
SELECT pg_catalog
Adrian Klaver writes:
> On 12/1/24 12:05, PopeRigby wrote:
>> I'm still getting this error:
>>
>> psql:all.sql:4102: ERROR: type "earth" does not exist
>> LINE 1: ...ians($1))*sin(radians($2))),earth()*sin(radians($1)))::earth
> The issue is still this:
> SELECT pg_catalog.set_config('search_pa
On 12/1/24 12:05, PopeRigby wrote:
On 11/30/24 19:58, Tom Lane wrote:
"David G. Johnston" writes:
Ok, so the error is not emanating from your code but rather the body
of the
ll_to_earth function defined in the earthdistance extension.
Yeah. That is
CREATE FUNCTION ll_to_earth(float8, float
PopeRigby writes:
> I've applied the following patch to postgres:
> https://www.postgresql.org/message-id/attachment/122092/0002-earthdistance-sql-functions.patch
Cool. You did actually install the new scripts into your target
installation, right?
> I'm still getting this error:
> psql:all.sql:
On 11/30/24 19:58, Tom Lane wrote:
"David G. Johnston" writes:
Ok, so the error is not emanating from your code but rather the body of the
ll_to_earth function defined in the earthdistance extension.
Yeah. That is
CREATE FUNCTION ll_to_earth(float8, float8)
RETURNS earth
LANGUAGE SQL
IMMUTAB
"David G. Johnston" writes:
> Ok, so the error is not emanating from your code but rather the body of the
> ll_to_earth function defined in the earthdistance extension.
Yeah. That is
CREATE FUNCTION ll_to_earth(float8, float8)
RETURNS earth
LANGUAGE SQL
IMMUTABLE STRICT
PARALLEL SAFE
AS 'SELECT
On Saturday, November 30, 2024, PopeRigby wrote:
>
> Ok, so the error is not emanating from your code but rather the body of
> the ll_to_earth function defined in the earthdistance extension.
>
> David J.
>
> By code do you mean my sql file created by pg_dumpall? Sorry, I'm just a
> self-hoster s
On 11/30/24 19:45, David G. Johnston wrote:
On Saturday, November 30, 2024, PopeRigby wrote:
On 11/30/24 18:41, David G. Johnston wrote:
On Saturday, November 30, 2024, PopeRigby
wrote:
On 11/30/24 17:27, David G. Johnston wrote:
On Saturday, November 30, 2024, P
On Saturday, November 30, 2024, PopeRigby wrote:
> On 11/30/24 18:41, David G. Johnston wrote:
>
> On Saturday, November 30, 2024, PopeRigby wrote:
>
>> 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 wro
CREATE EXTENSION cube;
I do not know if you might need this one as well. I am assuming that you
are working on a gist server.
CREATE EXTENSION earthdistance;
I am assuming you are working with a gist server. This ought to be useful.
https://gist.cs.berkeley.edu/pggist/
You might want to read t
On 11/30/24 18:41, David G. Johnston wrote:
On Saturday, November 30, 2024, PopeRigby wrote:
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 wrot
On 11/30/24 19:26, PopeRigby wrote:
On 11/30/24 18:41, David G. Johnston wrote:
On Saturday, November 30, 2024, PopeRigby wrote:
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/30/24 18:41, David G. Johnston wrote:
On Saturday, November 30, 2024, PopeRigby wrote:
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 wrot
On Saturday, November 30, 2024, PopeRigby wrote:
> 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 exi
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(
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(cub
On 11/29/24 17:47, Adrian Klaver wrote:
On 11/29/24 17:34, PopeRigby wrote:
My HDD recently failed so I'm trying to restore my backup, but I'm
running into some errors.
I've been using a systemd service that periodically backs up my
cluster with pg_dumpall, and I'm using this command to resto
On 11/29/24 17:34, PopeRigby wrote:
My HDD recently failed so I'm trying to restore my backup, but I'm
running into some errors.
I've been using a systemd service that periodically backs up my cluster
with pg_dumpall, and I'm using this command to restore:
sudo psql -f backup.sql postgres
I
On Fri, Nov 29, 2024 at 8:35 PM PopeRigby wrote:
> My HDD recently failed so I'm trying to restore my backup, but I'm
> running into some errors.
>
> I've been using a systemd service that periodically backs up my cluster
> with pg_dumpall, and I'm using this command to restore:
>
> sudo psql -f
My HDD recently failed so I'm trying to restore my backup, but I'm
running into some errors.
I've been using a systemd service that periodically backs up my cluster
with pg_dumpall, and I'm using this command to restore:
sudo psql -f backup.sql postgres
I'm getting this output:
https://gist
51 matches
Mail list logo
