From: | Martin Winkel <martin(at)tiogatours(dot)nl> |
---|---|
To: | Sergei Kornilov <sk(at)zsrv(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16534: autovacuum_autoanalyze not working on latitude(earth) expression |
Date: | 2020-07-12 09:46:49 |
Message-ID: | CAJ7TOS9=RQm1bUASXhOMVqk+SH+2gMMEdgDH4Ym2WPo0mYFNTg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I don't fully understand the matter, but how I read it, it is a
problem between extensions calling each other's functions? How is this
only an issue when the background workers are autovacuuming? When I
manually analyze the table, no errors whatsoever. Is this because of
the search path which is set when I execute the query from pgadmin?
Regards, Martin Winkel
________________________________
Van: Sergei Kornilov <sk(at)zsrv(dot)org>
verzonden: vrijdag 10 juli 2020 21:58
Aan: Tom Lane; martin(at)tiogatours(dot)nl
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Onderwerp: Re: BUG #16534: autovacuum_autoanalyze not working on
latitude(earth) expression
Hello
> Possibly at some point somebody will care enough to patch the module
> to attach "SET search_path" clauses to all the SQL functions.
I tried. But such idea was rejected because will prevent function
inlining, confuses relocated extensions, and fix only this extension.
https://www.postgresql.org/message-id/flat/15530-3dc5f66205393dc0%40postgresql.org
regards, Sergei
From | Date | Subject | |
---|---|---|---|
Next Message | Max Vikharev | 2020-07-12 12:06:31 | Re: postgresql 12 runs out of memory when updating a partitioned table with subquery |
Previous Message | David Rowley | 2020-07-12 05:50:29 | Re: postgresql 12 runs out of memory when updating a partitioned table with subquery |