Monday, April 22, 2019

[google-cloud-sql-discuss] Re: Postgres 11 ERROR could not resize shared memory segment

Quick update - setting the db flag random_page_cost to 1 seems to have gotten rid of the problems...for now at least.  I got the idea from this blog post - my understanding is that these instances are optimized for HDD even if SSD is used, resulting in terrible performance under some circumstances.  Changing random_page_cost to 1 fixes that.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/3c0362d2-32dc-43c2-86ca-da9900fadcdd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment