Re: pgbouncer best practices

: > Rita wrote on 7/8/23 4:27 AM: > > I am not sure if it allows transaction pooling. > > > Well, take the time to figure it out. With transaction pooling enabled, > you can get away with a much lower number of server connections. For > example, our application regularly

Re: pgbouncer best practices

I am not sure if it allows transaction pooling. On Fri, Jul 7, 2023 at 12:37 PM Ben Chobot wrote: > Rita wrote on 7/7/23 9:23 AM: > > I have an application that does many db calls from a server farm. I've > increased my max connections on postgresql to 1000 and tuned the server &

pgbouncer best practices

I have an application that does many db calls from a server farm. I've increased my max connections on postgresql to 1000 and tuned the server accordingly. However, I still get can't connect to postgresql some times. I installed pgbouncer on few servers in the farm. I pointed the traffic to

Re: pgbouncer

or so) during that time. On Wed, Jun 28, 2023 at 8:23 AM Sebastiaan Mannem wrote: > 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

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: recovery.conf and archive files

is the archive command even needed? I can see my standby fully synced. On Fri, Oct 14, 2022 at 5:27 AM Guillaume Lelarge wrote: > Le jeu. 13 oct. 2022 à 12:42, Rita a écrit : > >> The primary's recovery.conf looks like this >> >> listen_address='*' >> wal_level

Re: recovery.conf and archive files

, 2022 at 8:45 AM Guillaume Lelarge wrote: > Hi, > > Le dim. 9 oct. 2022 à 13:54, Rita a écrit : > >> I have primary and standby replication setup. >> >> On my primary the archive directory is rather large (30GB) and growing. >> On my st

recovery.conf and archive files

I have primary and standby replication setup. On my primary the archive directory is rather large (30GB) and growing. On my standby I have recovery.conf which has archive_cleanup_command = 'pg_archivecleanup -d /var/lib/pgsql/11/data/archive %r' I was under the impression this line would remove

Re: Pause streaming replication

://www.postgresql.org/docs/11/monitoring-stats.html#PG-STAT-REPLICATION-VIEW) ? I want to trigger an alert when 'streaming' isn't there. Or is there a better way to do it? On Wed, Nov 10, 2021 at 7:24 PM Ben Chobot wrote: > Rita wrote on 11/10/21 1:25 PM: > > Hello. > > > > I am testing a

Pause streaming replication

Hello. I am testing alerting on my primary and standby setup. I have async replication working but I would like to temporarily pause it so the value of 'state' isn't streaming. (select * from pg_stat_replication). How can I do that? -- --- Get your facts first, then you can distort them as

horizontal scaling

There was a lot of talk about horizontal scaling a few years ago. I was wondering if there have been any new efforts on it. -- --- Get your facts first, then you can distort them as you please.--

python async with psycopg2

I am trying to listen to multiple channels thru pg_notify mechanism. select pg_notify('mychan0',foo'); select pg_notify('mychan'1,'bar'); In python I have something like this import select,time import psycopg2 import psycopg2.extensions from psycopg2.extras import wait_select DSN="dbname=mydb

Re: Listen/Notify feedback

Good to know about potential performance problems. I don't plan to have more than 5 hosts. Also, good to know about MQTT. On Sun, Jul 12, 2020 at 8:52 AM Andrew Smith wrote: > On Sun, 12 Jul 2020 at 21:39, Rita wrote: > >> Thats good to know. Are there some standard patterns or be

Re: Listen/Notify feedback

t were mid-process during a crash. This is trickier with more > than one listener. This isn't a whole lot more efficient than just using > the table alone, but it saves you from having to poll so better response > times. > > On Sat, Jul 11, 2020 at 8:58 AM Rita wrote: > >>

Listen/Notify feedback

I am investigating various pub/sub tools such as ActiveMQ, Rabbit, Redis, etc.I came across Postgresql Listen/Notify and was easily able to write code to listen to messages. For the people who have been using this for a while: what are its downsides, things to consider when writing good code that

Re: what to do after a failover

with pg_rewind and I didn't like its complexity. On Wed, Jan 8, 2020 at 11:31 PM Michael Paquier wrote: > On Wed, Jan 08, 2020 at 11:06:28PM -0500, Rita wrote: > > I run a master and standby setup with Postgresql 11. The systems are > > identical from a hardware and software setup. If

what to do after a failover

I run a master and standby setup with Postgresql 11. The systems are identical from a hardware and software setup. If the master goes down I can do a pg_ctl promote on the standby and point my applications to use the standby (new master). Once the original master is online, when is an