Re: Wrong passwords allowed

On 6/28/23 17:45, Atul Kumar wrote: Hi, I am having a strange issue that I have a postgres intance running on version 12 in centos 7. So whenever I am trying to login in the database using psql -W option, I am entering the wrong passwords for that user, even after that I am logging in the d

Wrong passwords allowed

Hi, I am having a strange issue that I have a postgres intance running on version 12 in centos 7. So whenever I am trying to login in the database using psql -W option, I am entering the wrong passwords for that user, even after that I am logging in the database. So could you help me in telling

recovery_target_action = shutdown not working on PG11 during PITR restore

Hello! I'm attempting to restore a database (via pgbackrest) on PG11.20 and have the database shutdown when all of the WAL archives have finished applying. In my recovery.conf file I have recovery_target_action = 'shutdown' with an appropriate recovery target time and restore command setup. hot_st

Re: need explanation about an explain plan

On Wed, 2023-06-28 at 19:25 +0200, Marc Millas wrote: > Hi Laurenz, as said, in each partition there is only one value for ladate. The planner doesn't seem to take that into account. Yours, Laurenz Albe

Re: need explanation about an explain plan

On Wed, Jun 28, 2023 at 6:48 PM Laurenz Albe wrote: > On Wed, 2023-06-28 at 17:29 +0200, Marc Millas wrote: > > https://explain.depesz.com/s/Opk0 > > > > The big table (10 billions raws) is split in around 130 partitions, one > by month. > > the ladate column is the partition key, and it does hav

Re: need explanation about an explain plan

On Wed, 2023-06-28 at 17:29 +0200, Marc Millas wrote: > https://explain.depesz.com/s/Opk0 > > The big table (10 billions raws) is split in around 130 partitions, one by > month. > the ladate column is the partition key, and it does have 1 value for each > partition. > there is an index on the nu

Re: need explanation about an explain plan

Sorry, gmail sent uncompleted message Hi, Postgres 14.2 (for one more month) The explain plan and request is here: https://explain.depesz.com/s/Opk0 The big table (10 billions raws) is split in around 130 partitions, one by month. the ladate column is the partition key, and it does have 1 value

need explanation about an explain plan

Hi, Postgres 14.2 (for one more month) The explain plan and request is here: https://explain.depesz.com/s/Opk0 The big table is split in around 130 partitions, one by month. the ladate column is the partition key, and it does have 1 value for each partition. there is a Marc MILLAS Senior Arc

Re: pgbouncer

Laurenz Albe wrote on 6/28/23 5:27 AM: On Wed, 2023-06-28 at 07:19 -0400, Rita wrote: seems like I may need to deploy pgbouncer for my webapp. should i deploy it on the db server or on the webserver? On the database server. You don't want network latency between pgbouncer and PostgreSQL, so

Re: typical active table count?

Jeremy Schneider wrote on 6/27/23 11:47 AM: Thank Ben, not a concern but I'm trying to better understand how common this might be. And I think sharing general statistics about how people use PostgreSQL is a great help to the developers who build and maintain it. One really nice thing about Postg

Re: pgbouncer

I have a dedicated server. I have 3 additional physical application servers which hit the database. I periodically get the application server not able to reach the database server (is server on port 5432 listening? message). Looking at some metrics, seems like I am pulling a lot of tuples (300k or

Re: pgbouncer

On the DB server: the bouncer is made to optimize many and fast connections to the DB and fasten the throughput, so You've to have the shortest way to go to the data. One important thing: remember that different user raise different connections so be careful to choose which application you'll direc

Re: pgbouncer

On Wed, 2023-06-28 at 07:19 -0400, Rita wrote: > seems like I may need to deploy pgbouncer for my webapp. should i deploy it > on the db server or on the webserver? On the database server. You don't want network latency between pgbouncer and PostgreSQL, so that the connections can be active as

Re: pgbouncer

It greatly depends on what you want to achieve. Both have pro’s and con’s. What do you need pgbouncer for? Verstuurd vanaf mijn iPhone > Op 28 jun. 2023 om 13:19 heeft Rita het volgende > geschreven: > >  > > seems like I may need to deploy pgbouncer for my webapp. should i deploy it > on t

Re: LibPQ: PQresultMemorySize as proxy to transfered bytes

I wrote: > That number is the total space actually requested from malloc() for > the PGresult object. But we request space in blocks (typically 2KB > each), so there's some overhead due to fields not exactly filling > a block, unused space in the last block, etc. If you're testing > with very sma

pgbouncer

seems like I may need to deploy pgbouncer for my webapp. should i deploy it on the db server or on the webserver? -- --- Get your facts first, then you can distort them as you please.--

Re: LibPQ: PQresultMemorySize as proxy to transfered bytes

Dominique Devienne writes: > Obviously from these results, I now realize PQresultMemorySize() returns > something larger than what went across the network. Can someone explain > how so? That number is the total space actually requested from malloc() for the PGresult object. But we request space

Re: Replication between different 15.x minor versions ok?

On Wed, 2023-06-28 at 12:01 +0200, David Tinker wrote: > Is it ok to use physical replication between different 15.x minor releases > (on Ubuntu 22.04)? I haven't been able to find a definitive answer. Yes, that is OK. Yours, Laurenz Albe

Re: Replication between different 15.x minor versions ok?

Streaming replication between minor versions works perfectly fine. However, it's better to use same versions but different minor versions also work. Sent from Outlook for Android From: David Tinker Sent: Wednesday, June 28, 2023 3:02:22 p

Replication between different 15.x minor versions ok?

Is it ok to use physical replication between different 15.x minor releases (on Ubuntu 22.04)? I haven't been able to find a definitive answer. Thanks.

LibPQ: PQresultMemorySize as proxy to transfered bytes

Hi, To measure throughput, I'm timing exec time spent in LibPQ, against the size of the result-set in bytes, as reported by PQresultMemorySize(). *EXEC: 7x ( 130,867 rows, 54,921,532 bytes) in 0.305s (171.8 MB/s)* *EXEC: 8x ( 180,079 rows, 95,876,047 bytes) in 0.49