On Thu, 2023-11-02 at 09:12 +, Avi Weinberg wrote:
> I'm using Patroni Postgres installation and noticed that twice already
> postgres
> crashed due to out of memory. I'm using logical replication with around 30-40
> active subscribers on this machine. The machine has 128GB but only 32GB is
Hi Nikolay,
> On Nov 2, 2023, at 07:36, Nikolay Samokhvalov wrote:
> There is also a good trick described in
> https://www.crunchydata.com/blog/fun-with-pg_checksums to avoid
> accidental start of Postgres:
[...]
> Additionally, I compiled some thoughts about running pg_checksums
> without
Hi experts,
I'm using Patroni Postgres installation and noticed that twice already postgres
crashed due to out of memory. I'm using logical replication with around 30-40
active subscribers on this machine. The machine has 128GB but only 32GB is
allocated to Postgres. How can I know what is
Hi!
When I really want to use all the resources - I set the number of jobs to a
value equal to the number of CPU plus 1. Probably there is no reason to
make run more jobs than number of CPU :-) .
Unfortunately, pg_dump will not allocate more than one thread to a table,
even a huge one (unless it
On Mon, Oct 30, 2023 at 6:57 AM Alexander Kukushkin wrote:
...
> As Michael already said, the following workflow works just fine (I did it
> dozens of times):
> 1. enable checksums on the standby node
> 2. start the standby and let it catch up with the primary
> 3. switchover to a standby node
>
