Feature Request P2
Status Update
Comments
ma...@doit.com <ma...@doit.com> #2
I have forwarded your request to our engineering team. I cannot provide an E.T.A. or guarantee that this feature will be deployed. Rest assured that your feedback is always seriously taken. Any future updates will be posted on this thread.
ha...@google.com <ha...@google.com> #3
Is there any progress with that feature request?
tl...@google.com <tl...@google.com> #4
I'm also very interested in having this extension in cloudsql for postgres since it's blocking the emigration of one of ours databases
mo...@autotrader.co.uk <mo...@autotrader.co.uk> #5
+1 to voting for the ip4r extension. Currently not supported in Cloud SQL and we make use of it.
li...@google.com <li...@google.com> #6
Any updates on this? It's blocking a migration from RDS to google cloud.
Description
For example:
One chooses db-n1-standard-1 as the machine tier, which provides 3.75 GB RAM. But out of those 3.75 GB, some will be used by overhead processes.
Which means that one possibly hits memory limits when using only 3 GB of RAM with MySQL processes only.
Neither the documentation, nor the CloudSQL console graphs don't present these limits.