[google-cloud-sql-discuss] Re: default_time_zone

You can use something like:

SET GLOBAL time_zone = 'Europe/Paris';

In a cron task to be sure you are in the right timezone (summer and winter time).

On Monday, March 12, 2018 at 11:45:39 AM UTC+1, Silambarasan Sekar wrote:

Hi Team,

We are using Cloud SQL (mysql) second generation. We want our Cloud SQL instances to have Central Timezone.
The instances were have a database flag as "default_time_zone" as '-06:00' till now, since the day light started yesterday, we have to manually change the database flag of 'default_time_zone' to -05:00. The same happened on Nov 4th of 2017. 

The question I wanted to ask is, "Do we have to manually change the default_time_zone twice a year because of the day light savings or is there a mechanism in place that I am not aware of which will take care of this automatically." Thank you!

Thanks & Regards
Venu

--
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/8df19297-2575-4ee9-ba80-530a8f99a112%40googlegroups.com.

[google-cloud-sql-discuss] about Cloud SQL connection through Cloud Proxy

Hi,

I heard from someone that when we do new open request to Cloud SQL through Cloud Proxy, maxium number of new open request is 50 per second.

Is that correct?

Also, if we connect to Cloud SQL without Cloud Proxy, maxium number of new open request is same as WITH Cloud Proxy, 50/second.

Is that correct, too?

If you have any document that describes about limitation of new open request per seconds for Cloud SQL connection, can you please share it with me?

Because we can increase DB server spec, I am wondering you will have more capacity to connect Cloud SQL if we don't use Cloud Proxy.

Thanks,

Masa

--
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/dec3b685-f7ca-41d3-9019-21bda8af0cc2%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL Zero downtime Maintenance

Hi, We have used an Active-Passive configuration of Cloud SQL postgres. In a sense it means that I have 2 Cloud SQL master in the same region. One is primary which is responsible for the entire application. It has some read replicas. But during maintenance of master 1 and read replicas, I have a HAProxy to switch to a backup server. Our data is high read/less write scenario for which the data syncing to the master 2 can be done with export from master 1 and import into backup master 2. Once the maintenance is over, HAProxy switches it back to master 1. So practically I have zero downtime. There are other partner solutions Google can offer so you can get in touch with your Technical Account Manager.

On Monday, October 28, 2019 at 3:23:43 PM UTC+1, chen levi wrote:

Hi

looks like there is nothing we can do in order to enforce Zero downtime for our GCP Cloud SQL during maintenance window.

from what i've read seems like even adding Failover replicas will not help here as the replicas will have the same maintenance window, meaning they will both get down during maintenance.

also i assume read replicas also wont help here as read replicas are not ment for failover, although they have a different maintenance window (which can be anytime).

am i missing something?

thanks

Chen

--
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/1ecc7a3c-ed58-44e3-afa7-954c12e21ada%40googlegroups.com.

Re: [google-cloud-sql-discuss] Temporary IP access to SQL

That's true but I can't permit access via proxy to all my collaborators. I'm creating a GUI dedicated for IP authorization for my SQL access.

Thanks

Il giorno lunedì 28 ottobre 2019 19:08:08 UTC+1, Jarmo Isotalo ha scritto:

For a plain psql-cli access you can use `gcloud sql connect ... ` which automatically temporarily whitelists your IP for the connection.

Why the cloud-sql-proxy won't work in your case btw?

Cheers,

Jarmo

On Mon, Oct 28, 2019 at 8:02 PM Kappa <dek...@gmail.com> wrote:

Hi everyone!

Is there any way to set a public IP to access to a sql service for 1 hour?

 for example I'm working from home and I need to access directly to my database from my public home ip.

I found this setting but I need to transform it with a duration (something like a cron that remove the specific IP address)

I can't use proxy configuration

Thanks!

--
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/29cd8714-8717-4f51-ae8f-31775f5194a0%40googlegroups.com.

--
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/2c9af057-558f-4e1f-afea-7182956d436b%40googlegroups.com.

[google-cloud-sql-discuss] My Google AppEngine PHP application fail to connect to Google Cloud SQL at 10:42 29/10/2019 UTC+8

but I cannot find any error log in Cloud SQL and Appengine

do any one have the same issue?

--
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/1fac8d14-00e6-47ce-b6ad-e3cdbe8184e2%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL Zero downtime Maintenance

Short maintenance-related service interruptions do occur. You should design your applications to deal with situations when your instance is not accessible for short periods of time, such as in a maintenance shutdown. To minimize impact to your service, you can set a maintenance window to control when downtime occurs.

You can test the behavior of your application to a maintenance shutdown by restarting your instance, which has the same effect. In general, we recommend that you use only short-lived connections as well as use exponential back-off for retrying rejected connections. For more guidance see How should I manage connections?.

--
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/906a5a9c-15af-4c6b-8b50-a4b951bc481b%40googlegroups.com.

Re: [google-cloud-sql-discuss] Temporary IP access to SQL

For a plain psql-cli access you can use `gcloud sql connect ... ` which automatically temporarily whitelists your IP for the connection.

Why the cloud-sql-proxy won't work in your case btw?

Cheers,

Jarmo

On Mon, Oct 28, 2019 at 8:02 PM Kappa <dek4net@gmail.com> wrote:

Hi everyone!

Is there any way to set a public IP to access to a sql service for 1 hour?

 for example I'm working from home and I need to access directly to my database from my public home ip.

I found this setting but I need to transform it with a duration (something like a cron that remove the specific IP address)

I can't use proxy configuration

Thanks!

--
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/29cd8714-8717-4f51-ae8f-31775f5194a0%40googlegroups.com.

--
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/CANphD96HEURMHw3JPdBbvi13q-NvbNyV-QnKayY3_af5xKBB-g%40mail.gmail.com.

[google-cloud-sql-discuss] Temporary IP access to SQL

Hi everyone!

Is there any way to set a public IP to access to a sql service for 1 hour?

 for example I'm working from home and I need to access directly to my database from my public home ip.

I found this setting but I need to transform it with a duration (something like a cron that remove the specific IP address)

I can't use proxy configuration

Thanks!

--
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/29cd8714-8717-4f51-ae8f-31775f5194a0%40googlegroups.com.

[google-cloud-sql-discuss] Cloud SQL Zero downtime Maintenance

Hi

looks like there is nothing we can do in order to enforce Zero downtime for our GCP Cloud SQL during maintenance window.

from what i've read seems like even adding Failover replicas will not help here as the replicas will have the same maintenance window, meaning they will both get down during maintenance.

also i assume read replicas also wont help here as read replicas are not ment for failover, although they have a different maintenance window (which can be anytime).

am i missing something?

thanks

Chen

--
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/ee00f5fc-75be-428c-86fa-ab39ab69579c%40googlegroups.com.

[google-cloud-sql-discuss] Re: Connection issues using cloudsqlproxy and Cloud SQL 2 gen HA

Hello Yasser, thank you very much for your interaction!

Did anything change in terms of rate of connections to the instance?

No changes, same amount of connections etc for the las few months.

 

Aborted connections usually means connections to the database are not being terminated properly. Please see these docs [1][2].

Thanks! I will look into it. The app in question is a Wordpress.

We noticed that this error appears from time to time, but did not necessarily happen constantly.

 

The restart could be fixing the issue temporarily then the instance will do the same thing after the connections flood again.

During the incident, restarting did not solve our issue.

We had no connections at all between app and db servers.

 

But if you believe this is on the Google side, you can open a new issue here so that we can investigate further [3].

I will do that, thank you very much.

On Tuesday, October 22, 2019 at 2:31:27 PM UTC-3, Yasser Karout wrote:

Hello,

Did anything change in terms of rate of connections to the instance? Aborted connections usually means connections to the database are not being terminated properly. Please see these docs [1][2]. 

The restart could be fixing the issue temporarily then the instance will do the same thing after the connections flood again.

But if you believe this is on the Google side, you can open a new issue here so that we can investigate further [3].

[1] https://cloud.google.com/sql/docs/mysql/diagnose-issues#aborted-connection

[2] https://cloud.google.com/sql/docs/mysql/manage-connections

[3] https://issuetracker.google.com/

--
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/4247481f-8ac6-4947-a200-31ab724805fa%40googlegroups.com.

[google-cloud-sql-discuss] Re: Connection issues using cloudsqlproxy and Cloud SQL 2 gen HA

Hello,

Did anything change in terms of rate of connections to the instance? Aborted connections usually means connections to the database are not being terminated properly. Please see these docs [1][2]. 

The restart could be fixing the issue temporarily then the instance will do the same thing after the connections flood again.

But if you believe this is on the Google side, you can open a new issue here so that we can investigate further [3].

[1] https://cloud.google.com/sql/docs/mysql/diagnose-issues#aborted-connection

[2] https://cloud.google.com/sql/docs/mysql/manage-connections

[3] https://issuetracker.google.com/

--
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/cf0148e1-0a62-47c2-b3a8-45d30c82c84a%40googlegroups.com.

[google-cloud-sql-discuss] Re: Connection issues using cloudsqlproxy and Cloud SQL 2 gen HA

Images that broke are here.

Several updates being applied during incident:

Several updates being applied during incident:

On Tuesday, October 22, 2019 at 11:50:39 AM UTC-3, Jan Schnurle wrote:

Hi there!

We recently ran into networking issues between App servers on Compute Engine and SQL MYSql server (2 gen. HA).

This issue has affected us now two times and during the incident we are unable to connect to the SQL MYSql server via cloudsqlproxy or directly via IP.

During the incident we also noticed several updates being applied to the SQL MYSql 2 Gen server, even if out of the scheduled update time, (evidence further below).

Please note that we did not face any kind of networking issues since the deployment of the infrastructure, which happened ~14 moths ago.

Evidence of connection issues:

• 2019/10/17 07:18:32 couldn't connect to "#######-website:us-east1:#####mysql01": dial tcp ########:3307: getsockopt: connection timed out

Example of logs collected on the Cloud SQL console:

• Aborted connection ###### to db: '######' user: '#######' host: 'cloudsqlproxy~########' (Got an error reading communication packets)
• Slave I/O for channel: error reconnecting to master 'cloudsqlreplica@#########:3306' - retry-time: 60  retries: 1, Error_code: 2003

Several updates being applied during incident:

Updates being applied outside planned window:

Solution:

The only way to reestablish the connection between App servers and SQL MYSql server was manually triggering the failover.

Once the process completes, the connection is reestablished and works as expected.

Did anybody out there face the same issue?

Thank you very much!

--
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/f9c73f8f-2e0e-4e5c-b765-683b88809ef3%40googlegroups.com.

[google-cloud-sql-discuss] Connection issues using cloudsqlproxy and Cloud SQL 2 gen HA

Hi there!

We recently ran into networking issues between App servers on Compute Engine and SQL MYSql server (2 gen. HA).

This issue has affected us now two times and during the incident we are unable to connect to the SQL MYSql server via cloudsqlproxy or directly via IP.

During the incident we also noticed several updates being applied to the SQL MYSql 2 Gen server, even if out of the scheduled update time, (evidence further below).

Please note that we did not face any kind of networking issues since the deployment of the infrastructure, which happened ~14 moths ago.

Evidence of connection issues:

• 2019/10/17 07:18:32 couldn't connect to "#######-website:us-east1:#####mysql01": dial tcp ########:3307: getsockopt: connection timed out

Example of logs collected on the Cloud SQL console:

• Aborted connection ###### to db: '######' user: '#######' host: 'cloudsqlproxy~########' (Got an error reading communication packets)
• Slave I/O for channel: error reconnecting to master 'cloudsqlreplica@#########:3306' - retry-time: 60  retries: 1, Error_code: 2003

Several updates being applied during incident:

Updates being applied outside planned window:

Solution:

The only way to reestablish the connection between App servers and SQL MYSql server was manually triggering the failover.

Once the process completes, the connection is reestablished and works as expected.

Did anybody out there face the same issue?

Thank you very much!

--
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/50bfe831-c6bf-47ef-9673-3ada33a26ab2%40googlegroups.com.

[google-cloud-sql-discuss] Re: Decrease performance when conecting to Cloud SQL via proxy

Further investigating this latency issue, more in depth, requires communicating of private information such as project names. Publicly postings in Groups are not suitable for this level of information exchange. You are encouraged to open a private issue of similar content in Public Issue Tracker. You should choose a PIT component marked as „private", to secure appropriate levels of privacy for your data. 

--
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/4f514aea-f8cb-4a7a-8483-81e9a754e43e%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Export and import fails with ERROR: temporary file size exceeds temp_file_limit

Thanks! We were just confused about how creating and trying to restore an instance with the default settings failes. 

Cheers,

Jarmo

On Fri, Oct 18, 2019 at 2:04 AM 'Amit Sinha' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

Hello Jarmo, as you already figure out the flag, I am sharing the document related to this which might be helpful for the details [1]

[1] https://cloud.google.com/sql/docs/postgres/flags#list-flags-postgres

On Wednesday, October 16, 2019 at 11:05:53 AM UTC-4, Jarmo Isotalo wrote:

I realized we can tweak that setting under the database flags

--
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/4add93e8-1ce8-4a77-9419-3f1e6e3838a9%40googlegroups.com.

--
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/CANphD94y31XJMxT_qWjqb8Z_ypWUQDmUwK7G2VNrM%2BGb7fdzUg%40mail.gmail.com.

[google-cloud-sql-discuss] Re: Export and import fails with ERROR: temporary file size exceeds temp_file_limit

Hello Jarmo, as you already figure out the flag, I am sharing the document related to this which might be helpful for the details [1]

[1] https://cloud.google.com/sql/docs/postgres/flags#list-flags-postgres

On Wednesday, October 16, 2019 at 11:05:53 AM UTC-4, Jarmo Isotalo wrote:

I realized we can tweak that setting under the database flags

--
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/4add93e8-1ce8-4a77-9419-3f1e6e3838a9%40googlegroups.com.

[google-cloud-sql-discuss] Re: Ghost deployment: Connect Issue ENOENT & Unknown database error

Can you check to make sure the permissions for the GAE service account are set properly? [1]

Development questions are usually better addressed on Stackoverflow since they will have better visibility.

[1] https://cloud.google.com/sql/docs/mysql/connect-app-engine#configuring

--
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/2748726a-8487-4b3e-ae03-bc9af1cf06d6%40googlegroups.com.

[google-cloud-sql-discuss] Ghost deployment: Connect Issue ENOENT & Unknown database error

I have a nodejs app and followed the instructions in this https://cloud.google.com/community/tutorials/ghost-on-app-engine-part-1-deploying for the deployment

I can test it locally and I am able to connect through the cloudsqlproxy. But When I try to deploy it I am getting the following error:

 ERROR connect ENOENT /cloudsql/YOUR_INSTANCE_NAME

"Unknown database error"

Error: connect ENOENT /cloudsql/YOUR_INSTANCE_NAME

    at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1106:14)

1. Enabled Cloud SQL Admin Api

2. Added the config changes in the app.yaml

Can someone help me with this?

--
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/af531e61-085b-49ca-b887-96de2af4bb39%40googlegroups.com.

[google-cloud-sql-discuss] Re: Decrease performance when conecting to Cloud SQL via proxy

Thanks for your reply. I compare with response time when I call an API from my application between new and old infrastructure and see connect to Cloud SQL slower

than manual Postgres installation in GCE.

I already try 3 and 4 I got the same response time.

Other information looks like response time increases when it has low traffic at midnight.

How can I improve this? 

เมื่อ วันพุธที่ 16 ตุลาคม ค.ศ. 2019 23 นาฬิกา 51 นาที 22 วินาที UTC+7, George (Cloud Platform Support) เขียนว่า:

How did you establish that application performance is decreasing when connecting to Cloud SQL from GKE? What did you compare your measurement data to? More details are needed for a proper investigation. 

To move forward with such an investigation, following information is needed, and has to be verified: 

1. Project-id.

2. Name of the Cloud SQL instance and VM instances.

3. Verify the Cloud SQL connection latency directly from GKE instances using IP address.

3. Verify the network latency directly from both GKE instances (as you mentioned above) to Cloud SQL instance using ping.

4. Verify if you experience same latency when you connect to the Cloud SQL using the Cloud SQL Proxy.

Information and verification implied at the 4 points above requires a high level of privacy in exchanging messages. This is not possible in publicly visible forums as here in Groups. In Public Issue Tracker you may opt for "private issue", and maintain desired level of privacy. You are encouraged to open a new private issue in Tracker, with information described at the 4 points above.  

--
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/922b4f81-99ef-4104-b31a-433750acfcfb%40googlegroups.com.

[google-cloud-sql-discuss] Re: Unable to Create Cloud SQL instance or connect to Existing Cloud SQL Instance in Asia Region

Hello Nikunj, 

I can see some updates today in the issue you created. Please reply back to the issue to we can proceed with the investigation. 

On Tuesday, October 15, 2019 at 7:22:59 PM UTC-4, Nikunj Thakkar wrote:

Hi Julie,

Thanks for you reply. I have already provided all required details here: https://issuetracker.google.com/issues/142220356

Let me know if you need any further information.

Thanks,

Nikunj

On Monday, October 14, 2019 at 11:24:45 PM UTC+5:30, Julie (cloud platform support) wrote:

Thanks for reporting this. This is likely related to a known issue so please provide your project id when creating an private issue tracker so we can begin investigating this, as it will likely require exchange of sensitive or personal information. 

--
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/4c5f42e1-c95f-4438-8a21-5d3e2647fe76%40googlegroups.com.

[google-cloud-sql-discuss] Re: An unknown error occurred

Hello Ory,

Do you still have the issue? If Yes, I would recommend to open a private Cloud SQL issue in issue tracker providing more details about the issue and the time-frame when the issue occurred. Also please provide the project and the instance name having this issue so we can investigate further.

On Tuesday, October 15, 2019 at 7:22:59 PM UTC-4, Ory Purhonen wrote:

Hi,

Everything was working fine with our instance until yesterday. 

Yesterday we tried exporting the database but received a "An unknown error occurred".

Now the daily automatic backups are also receiving a "An unknown error occurred" error.

Tried restarting, but that gives the same error.

Can I please get some help with this?

Kind Regards,

Ory

--
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/2f2760d1-9484-40a4-8633-948b7e60b1b5%40googlegroups.com.

[google-cloud-sql-discuss] Re: Update to MySQL 5.7.22

You can also use these Issue Tracker links to stay up to date about the releases.

[1] https://issuetracker.google.com/79910725

[2] https://issuetracker.google.com/139410963

--
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/a9d0f18e-1f83-4fa5-a65b-3163623fedd4%40googlegroups.com.

[google-cloud-sql-discuss] Re: Decrease performance when conecting to Cloud SQL via proxy

How did you establish that application performance is decreasing when connecting to Cloud SQL from GKE? What did you compare your measurement data to? More details are needed for a proper investigation. 

To move forward with such an investigation, following information is needed, and has to be verified: 

1. Project-id.

2. Name of the Cloud SQL instance and VM instances.

3. Verify the Cloud SQL connection latency directly from GKE instances using IP address.

3. Verify the network latency directly from both GKE instances (as you mentioned above) to Cloud SQL instance using ping.

4. Verify if you experience same latency when you connect to the Cloud SQL using the Cloud SQL Proxy.

Information and verification implied at the 4 points above requires a high level of privacy in exchanging messages. This is not possible in publicly visible forums as here in Groups. In Public Issue Tracker you may opt for "private issue", and maintain desired level of privacy. You are encouraged to open a new private issue in Tracker, with information described at the 4 points above.  

--
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/2d1a8fd4-743c-4477-a3c7-824128fccb11%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL MySQL 2nd Gen Regional Disks?

Implementation of newer MySQL versions are being worked on. You can stay up to date using these issue tracker links [1][2].

[1] https://issuetracker.google.com/79910725

[2] https://issuetracker.google.com/139410963

--
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/4d9106d4-ebc7-48e5-a5bf-b8052dbc3321%40googlegroups.com.

[google-cloud-sql-discuss] Re: Update to MySQL 5.7.22

Over a year later and still no update...how can Google Cloud be moving so slow?

On Friday, June 29, 2018 at 10:43:12 AM UTC-4, Dinesh (Google Platform Support) wrote:

Hi Robert,

Fortunately, I don't have an ETA when Cloud SQL version 5.7.22 will be available. However, you can keep tracking Cloud SQL release notes[1] for the major changes to Cloud SQL including version updates.   

I hope it helps. 

Regards,

[1]: https://cloud.google.com/sql/docs/release-notes

On Thursday, June 28, 2018 at 9:11:00 AM UTC-4, Robert Herhold wrote:

Hi,

I need to use a feature that was released in MySQL 5.7.22 (released 4/19/18), but my Cloud SQL instance is on version 5.7.14. When are updates to Cloud SQL typically released, and when can I expect to be able to update to 5.7.22?

Thanks

--
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/21c50a4a-46d5-4554-83fe-7160b960eeb8%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL MySQL 2nd Gen Regional Disks?

I hope so...the MySQL setup on cloud SQL is falling way behind competitors...5.7.14 was released over 3 years ago....get it together cloudsql team, you are getting left behind in the dust!

On Thursday, October 10, 2019 at 1:09:50 PM UTC-4, Yasser Karout wrote:

The rollout will still happen however it has been delayed. Emails will be sent by the team containing more details. Apologies for the inconvenience.

--
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/8db7a488-4730-45ef-afcb-b8d2c4303552%40googlegroups.com.

[google-cloud-sql-discuss] Re: Export and import fails with ERROR: temporary file size exceeds temp_file_limit

I realized we can tweak that setting under the database flags

--
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/c16e3599-7a1c-42eb-8ac0-750480110fa8%40googlegroups.com.

[google-cloud-sql-discuss] Decrease performance when conecting to Cloud SQL via proxy

I have to migrate from old infrastructure and use Cloud SQL in my first choice.

So I found my application performance decreasing when connecting to Cloud SQL from GKE.

So anyone can suggest or help me to configure this issue?

FYI, application uses PHP and database uses Postgres.

--
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/d7530bc7-9e36-4691-9cd2-2ceaad734815%40googlegroups.com.

[google-cloud-sql-discuss] Export and import fails with ERROR: temporary file size exceeds temp_file_limit

Hi All,

We were just trying to use the export to bucket and import from bucket features to migrate data from an PostgreSQL 9.4 instance to a fresh PostgreSQL 11 instance.

However, after importing for about 10 minutes the import failed with  

ERROR: temporary file size exceeds temp_file_limit (1541626kB) CONTEXT: parallel worker Import error: exit status 3

The source dataset is fairly small at 17G reported by the storage usage.

ps. Is there a better place to report issues like this; we are still waiting for the activation of our paid role-based support...

--
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/934da4da-432c-4d48-9626-cc02c9884f9b%40googlegroups.com.

[google-cloud-sql-discuss] Re: Unable to Create Cloud SQL instance or connect to Existing Cloud SQL Instance in Asia Region

Hi Julie,

Thanks for you reply. I have already provided all required details here: https://issuetracker.google.com/issues/142220356

Let me know if you need any further information.

Thanks,

Nikunj

On Monday, October 14, 2019 at 11:24:45 PM UTC+5:30, Julie (cloud platform support) wrote:

Thanks for reporting this. This is likely related to a known issue so please provide your project id when creating an private issue tracker so we can begin investigating this, as it will likely require exchange of sensitive or personal information. 

--
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/ceea3c27-bfb8-4691-bc71-c5e736faef8a%40googlegroups.com.

[google-cloud-sql-discuss] Re: memcache implementation

Hello Binaya, 

Do you use Standard Environment? You seem to want to use Memcache with Python 3.5. It is worthwhile noting that the actual App Engine version of Python is 3.7. In any case, Python 3 in Standard Environment does not offer facilities such as Memcache. To build an application cache, create a Cloud Memorystore instance and connect it to your app using Serverless VPC Access, as detailed on the Understanding differences between the Python 2 and Python 3 environments page. 

--
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/a027760c-ae77-43b9-a40a-417933a37f05%40googlegroups.com.

[google-cloud-sql-discuss] Re: Unable to Create Cloud SQL instance or connect to Existing Cloud SQL Instance in Asia Region

Thanks for reporting this. This is likely related to a known issue so please provide your project id when creating an private issue tracker so we can begin investigating this, as it will likely require exchange of sensitive or personal information. 

--
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/a5a7d016-c694-41f9-ae5e-c57c4ea37f9d%40googlegroups.com.

[google-cloud-sql-discuss] memcache implementation

I am not able to import these below google api

from google.appengine.api import memcache

This is throwing below error:

Traceback (most recent call last):

  File "<stdin>", line 1, in <module>

ImportError: No module named 'google.appengine'

My python version is 3.5

google-api-core (1.5.2)

google-auth (1.6.1)

google-cloud (0.34.0)

google-cloud-core (0.28.1)

google-cloud-storage (1.13.0)

google-compute-engine (2.8.3)

google-pasta (0.1.7)

google-resumable-media (0.3.1)

googleapis-common-protos (1.5.5)

Please help me, to implement the app-engine , memcache.

Thanks in advance.

--
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/4ef072c4-b694-4998-a73f-c314f237b9df%40googlegroups.com.

[google-cloud-sql-discuss] An unknown error occurred

Hi,

Everything was working fine with our instance until yesterday. 

Yesterday we tried exporting the database but received a "An unknown error occurred".

Now the daily automatic backups are also receiving a "An unknown error occurred" error.

Tried restarting, but that gives the same error.

Can I please get some help with this?

Kind Regards,

Ory

--
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/b17b3d96-d120-4909-bfbf-9d4edad76cb5%40googlegroups.com.

[google-cloud-sql-discuss] Re: can we use UDFs with managed Cloud MySQL?

Cloud SQL instances run in a managed environment. A UDF contains code that becomes part of the running server, which is difficult to accommodate in this environment. Why is this feature needed for your project? Is there no other option available? A feature request needs the support of a well-motivated use-case to prove its point and convince. A detailed description, preferably in step-by-step format, would be appreciated. Feature requests are closely examined and followed in the Public Issue Tracker, you are encouraged to open one there. 

--
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/11b31eb3-aa9b-4b96-8139-b7172adb36bc%40googlegroups.com.

[google-cloud-sql-discuss] Re: Guys, Where are my Posts, I am trying to find the posts I have created and posted here ? Where can I see them

Hello,

You should receive an email once someone replies to your post. Otherwise you can follow these steps as well [1].

https://webapps.stackexchange.com/questions/16407/see-all-my-posts-across-all-google-groups

--
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/677f3d7f-4358-4e78-b8a0-aa4447d8caa0%40googlegroups.com.

[google-cloud-sql-discuss] Re: Point in Time Recovery for Cloud SQL for PostgreSQL

Hello,

You can follow the following thread to stay up to date about PostgresSQL Point in Time recovery [1]. 

For Spanner the recommended method is the import/export feature to GCS [2][3]. You can use the Cloud Dataflow connector [4] to move data from Spanner to GCS periodically but this requires manual work and coding running Dataflow pipelines on your own.

Spanner also has global replication [5] meaning the data will always be available if one site is down and has strong consistency [6]. 

So based on your requirements, Spanner would likely be your best option. You can see a table comparing all database solutions as well here [7].

[1] https://issuetracker.google.com/78448400

[2] https://cloud.google.com/spanner/docs/import

[3] https://cloud.google.com/spanner/docs/export

[4] https://cloud.google.com/spanner/docs/dataflow-connector

[5] https://cloud.google.com/spanner/docs/replication#benefits_of_cloud_spanner_replication

[6] https://cloud.google.com/spanner/docs/true-time-external-consistency

[7] https://cloud.google.com/products/databases/

--
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/b64d2512-3f9c-404a-b4be-4d01ecf9f38e%40googlegroups.com.

[google-cloud-sql-discuss] Re: My cloud sql update frequently

How did you establish that there is maintenance happening almost everyday, on your Cloud SQL instance? Disruptive updates generally only occur every few months. 

If you think there is a problem with your Cloud SQL instance, your are encouraged to open an issue in the Public Issue Tracker, where communication can be set to private, and your project examined thoroughly for specific issues. This discussion group is oriented more towards general opinions, trends, and issues of general nature touching App Engine and Cloud SQL. For MySQL instance related advice, you may be better served in dedicated forums such as stackoverflow, where experienced programmers are within reach and ready to help. 

--
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/a8a8e372-1074-435a-9937-502e5ae745dc%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL MySQL 2nd Gen Regional Disks?

The rollout will still happen however it has been delayed. Emails will be sent by the team containing more details. Apologies for the inconvenience.

--
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/c56cceaf-5be6-4e0b-b59a-06975c8099be%40googlegroups.com.

[google-cloud-sql-discuss] Re: importing database doesn't create views/functions/procedures -- how to programatically create them?

Hello Tim, 

As you rightly point out, documentation indicates you need to re-create triggers manually, that is: if you export and then import data. Depending on your use-case and practical needs, you might be able to rather replicate your data to another MySQL instance by setting up replication. This can be accomplished in practice from your Cloud SQL instance directly to a Cloud SQL instance, or using the external master feature as an intermediate step.

This discussion group is oriented more towards general opinions, trends, and issues of general nature touching App Engine and Cloud SQL. For coding and programming architecture, as well as exporting and importing MySQL data, you may be better served in dedicated forums such as stackoverflow, where experienced programmers are within reach and ready to help. 

--
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/714678b1-505d-4789-aec3-2182b2081858%40googlegroups.com.

[google-cloud-sql-discuss] Guys, Where are my Posts, I am trying to find the posts I have created and posted here ? Where can I see them

Guys, Where are my Posts, I am trying to find the posts I have created and posted here ? Where can I see them. If anyone replies, I cannot even see the reply to this post. 

--
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/dfe2f787-811d-417d-8ba1-09526d644a47%40googlegroups.com.

[google-cloud-sql-discuss] Point in Time Recovery for Cloud SQL for PostgreSQL

Point in Time recovery is not yet available for Cloud SQL for PostgreSQL, however this is available for Cloud SQL for SQL. 

And may be available for Cloud Spanner (I do not know yet)?

=================

Here the situation is I want to achieve zero downtime year over year for my database.Let me start with cloud spanner: I can use cross region replication, however the issue would be with the operator errors like for example if an operator error causes a loss of data, I should be in a position to recover a database to its state before the error occurred.

I should be able to create stored procedures, restore any accidentally dropped/truncated tables, DB should be PCI compliant, support for SOAP/REST APIs,  a failover solution for a minute if google's infrastructure fails for a minute.

What do you guys think, could be a good option ?

--
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/e5de6631-d644-4dab-8712-b977b21ebb09%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL MySQL 2nd Gen Regional Disks?

Looks like the rollout has been cancelled....how does something being planned for this long just get scrapped at the last minute?

On Friday, September 27, 2019 at 11:16:16 AM UTC-4, Yasser Karout wrote:

Hello,

Communications will be sent out to customers soon regarding the roll out. Thanks for your patience.

--
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/56f8b270-35b1-43c5-a968-9307f1688c07%40googlegroups.com.

[google-cloud-sql-discuss] My cloud sql update frequently

 my cloud SQL update almost everyday.

I have set the  mainTenance time in sunday but it do not work.

Can anyone can help me?

--
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/0e253048-5914-4aa3-9b59-b144b9c12d3f%40googlegroups.com.

[google-cloud-sql-discuss] importing database doesn't create views/functions/procedures -- how to programatically create them?

When importing data into a Cloud MySQL, the documentation says that triggers, stored procedures, functions, and views must be recreated manually. What is a way to do create views/functions/procedures/events/triggers programatically (via script or program) so I don't have to do this literally manually for hundreds of views, procs, functions, etc?

--
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/c4d99916-8a3e-4d21-a8e3-ed8baae0a0ba%40googlegroups.com.

[google-cloud-sql-discuss] can we use UDFs with managed Cloud MySQL?

Is it possible to make a user-defined function for a managed MySQL? It looks like not -- are there any workarounds or plans to add this capability? 

--
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/dc91631c-d8b7-4fad-a1e2-be19a07ef27a%40googlegroups.com.

[google-cloud-sql-discuss] Unable to Create Cloud SQL instance or connect to Existing Cloud SQL Instance in Asia Region

Hi there,

We're facing an issue with connecting to our Cloud SQL instance in region asia-south1-b. We also tried to create new instances and it's repeatedly failing. Is anyone else facing similar issues? Can someone from Google Cloud team help in this regard?

I'm attaching screenshot for more details.

-- Nikunj

--
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/dea2f03f-8252-44a5-9355-78d41365e44c%40googlegroups.com.

[google-cloud-sql-discuss] Re: not understand my log error for deploy on gcloud

Hi,

Based on the logs provided, the issue seems to be related to the pip installation. I would suggest to check your requirements.txt file and make sure the right pip version is specified in there. For more information on this issue, you can refer to this page.

--
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/83fe3ef8-e496-4170-89c3-d3563c165697%40googlegroups.com.

[google-cloud-sql-discuss] Re: Google cloud sql service can not drop database

I would suggest to refer to this Stackoverflow thread, as the issue has already been discussed by the community and solutions were proposed to resolve the issue.

--
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/10196bde-2784-48e4-b9f7-4003a60e754e%40googlegroups.com.

[google-cloud-sql-discuss] Re: Recover from a removed SQL instance

You may benefit from automated backups, if this feature has been enabled for your instance; worthwhile checking, as your data might have been backed up this way. You cannot restore a deleted instance other than by re-creation, neither from an empty dump. You may gather more information on automated backups from the "Overview of backups" documentation page. 

--
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/77a70fd3-abf5-48cf-b6ec-0c8e0e0fe782%40googlegroups.com.