Please try the possible solutions suggested in this StackOverflow post.
Tried the random_page_cost but that didn't work for my query.
On Tuesday, April 23, 2019 at 3:31:23 AM UTC+1, Nick Fellows wrote:We just upgraded to the new Postgres 11 image from 9.6 and are dealing with a flood of the below error (with varying memory sizes) across multiple queries:org.postgresql.util.PSQLException: ERROR: could not resize shared memory segment "/PostgreSQL.78044234" to 2097152 bytes: No space left on device
I know that there were a lot of changes under the hood in PG 10 that potentially account for this, and it appears that the most common solution to the problem is to increase shared memory, which seems to be impossible to do with Google Cloud SQL. Is this a problem anyone else is dealing with, and if so, is there anything we can do on our end, outside of refactoring our queries to be simpler?
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/23788ee1-6e15-4a8d-8306-dca836b238bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment