Thank you.
Yes, I tried creating a table manually with column timestamptz(6) type and
partitioned on that and then executed select query with the filter on that
column and I do see partition pruning happening. Not able to visualize any
other issues though, however some teammates say it may have a
On Tue, Mar 5, 2024 at 1:09 AM sud wrote:
>
> However the question we have is ,
> 1)If there is any downside of having the partition key with "timestamp
> with timezone" type? Will it impact the partition pruning of the queries
> anyway by appending any run time "time zone" conversion function du
>
> We were planning to have the auto_explain extension added and set the
> log_min_duration to ~5 seconds and log_analyze to true. So that all the
> queries going above that time period will be logged and provide detailed
> information on the exact point of bottleneck. Will it be a good idea to se
On Tue, Mar 05, 2024 at 09:13:48AM +0100, Frank Lanitz wrote:
I don't actually know pgbadger, but:
> $ pgbadger --journalctl "journalctl -u postgresql.service"
> LOG: Ok, generating html report...s: 0, events: 0
Try as root? Or is pgbadger a setuid program?
--
Ian
Greetings,
* Matthew Dennison (m...@matty-uk.co.uk) wrote:
> Host file looks like:
>
> 127.0.0.1 localhost hostname hostname.mydomain.net
> ::1 localhost hostname hostname.mydomain.net
> 10.204.50.65 hostname hostname.mydomain.net
>
> I also tried commenting out the ::1 line, but the i
My apologies, when I said:
"When logging the input values, we can see that there are indeed two times
the same value sets (exactly the same)"
It seems I was wrong, the UUIDs differed on 1-2 characters which means that the
problem lies elsewhere in the system. It does seem that my assumptions of
On Tue, 2024-03-05 at 11:37 +, M Tarkeshwar Rao wrote:
> We want to use libpq library APIs only. Is there any support of keepalive at
> client side?
Yes, there is.
Just add "keepalives_idle=60" to the connection string. See
https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-KE
Hi Matthias,
Currently many customers are using this.
We want to use libpq library APIs only. Is there any support of keepalive at
client side?
Regards
Tarkeshwar
-Original Message-
From: Matthias Apitz
Sent: Tuesday, March 5, 2024 4:59 PM
To: M Tarkeshwar Rao
Cc: pgsql-gene...@post
El día martes, marzo 05, 2024 a las 11:08:27 +, M Tarkeshwar Rao escribió:
> Hi all,
>
> "
> We are using libpq c client (Version : 14.10) of postgresql in our
> application to connect with postgresql database server (Version 14.10).
> For making connection we are using libpq's API "PQsetdbL
Hi all,
"
We are using libpq c client (Version : 14.10) of postgresql in our application
to connect with postgresql database server (Version 14.10).
For making connection we are using libpq's API "PQsetdbLogin()".
Problem Statement : If our connection remains idle for more than 15 minutes,
then
M Tarkeshwar Rao would like to recall the message, "Connection remains idle for
more than 15 minutes, then the connection drops by IPVS setting in k8s
kube-proxy".
Hi Tarkesh,
"
We are using libpq c client (Version : 14.10) of postgresql in our application
to connect with postgresql database server (Version 14.10).
For making connection we are using libpq's API "PQsetdbLogin()".
Problem Statement : If our connection remains idle for more than 15 minutes,
Hello,
I think I just might did a small configuration issue, but somehow I cannot
figure it out by myself.
I want to let pgbadger directly fetch data from journald -- so I was using with
a unexpected outcome:
$ pgbadger --journalctl "journalctl -u postgresql.service"
LOG: Ok, generating html
13 matches
Mail list logo