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
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
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
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
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?
tting this output:
https://gist.github.com/poperigby/d5a0103b9de1eba95aba783007e557ea
This is my (redacted) database dump:
https://gist.github.com/poperigby/fcb59eb6c22c6051800e06a0ec482b49
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 u
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))*s
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
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
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
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 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: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
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
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
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 t
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
18 matches
Mail list logo
