Justin Pryzby writes:
> f2d0c7f18 should be backpatched to v15.
Agreed, done.
regards, tom lane
Thanks! This helps.
On Thu, Nov 3, 2022, 18:40 Alvaro Herrera wrote:
> On 2022-Nov-03, Tom Lane wrote:
>
> > Stefan Badenhorst writes:
> > > I am using a prometheus exporter:
> > > https://github.com/prometheus-community/postgres_exporter/
> >
> > Hmm, well, maybe prometheus is doing something
On 2022-Nov-03, Tom Lane wrote:
> Stefan Badenhorst writes:
> > I am using a prometheus exporter:
> > https://github.com/prometheus-community/postgres_exporter/
>
> Hmm, well, maybe prometheus is doing something with that part of the URL.
> There's no such behavior in Postgres itself, though.
Y
I am using a prometheus exporter:
https://github.com/prometheus-community/postgres_exporter/
Turning JIT off definitely made a big difference to all our environments.
When using JIT it causes OOM on postgres server after a few days. Adding
jit=off resolved the issue.
I have tested this now for seve
Stefan Badenhorst writes:
> I am using a prometheus exporter:
> https://github.com/prometheus-community/postgres_exporter/
Hmm, well, maybe prometheus is doing something with that part of the URL.
There's no such behavior in Postgres itself, though.
regards, tom lane
Stefan Badenhorst writes:
> This is working:
> postgresql://USERNAME:PASSWORD@server
> :5432/the_database?sslmode=disable&jit=off
Again, not for me:
$ psql 'postgresql://postgres@localhost:5432/mydb?sslmode=disable&jit=off'
psql: error: invalid URI query parameter: "jit"
I suspect something in
This is working:
postgresql://USERNAME:PASSWORD@server
:5432/the_database?sslmode=disable&jit=off
Maybe I was looking at the wrong documentation page?
On Thu, 3 Nov 2022 at 14:58, Tom Lane wrote:
> PG Doc comments form writes:
> > On this page:
> >
> https://www.postgresql.org/docs/current/libp
PG Doc comments form writes:
> On this page:
> https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-PARAMKEYWORDS
> There is a list of keywords that can be specified as part of the connection
> string.
> Specifying `jit=off` or `jit=on` is functional in practice, but `jit` is
> not i
On Thu, Jul 21, 2022 at 12:19:59PM +0900, Fujii Masao wrote:
> On 2022/07/20 16:26, Michael Paquier wrote:
> > On Wed, Jul 20, 2022 at 01:51:36PM +0900, Fujii Masao wrote:
> > > Attached is the updated version of the patch. It separates the list
> > > for GUC flags from the table entry for pg_setti
On Wed, 2022-11-02 at 19:29 +, David Burns wrote:
> To Whom It May Concern;
It concerns me, because I often see questions from people who misunderstand
this.
> Some additional clarity in the versions 14/15 documentation would be helpful
> specifically
> surrounding the "target_role" clause
To Whom It May Concern;
Some additional clarity in the versions 14/15 documentation would be helpful
specifically surrounding the "target_role" clause for the ALTER DEFAULT
PRIVILEGES command. To the uninitiated, the current description seems vague.
Maybe something like the following would he
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/libpq-connect.html
Description:
On this page:
https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-PARAMKEYWORDS
There is a list of keywords that can be specified as part of t
12 matches
Mail list logo
