[google-cloud-sql-discuss] Re: Can I encrypt MySQL at the Schema / DB level?

I could not find any documentation that Cloud SQL supports encryption at the schema level, however, you can implement column level Client-side encryption which is encrypting data before writing it to Cloud SQL. 

On Saturday, April 24, 2021 at 9:24:29 AM UTC-4 Benjamin Taub wrote:

We have developed a data matching application where each user can upload their data and use the features we provide. While it will change in the future, we are currently built on MySQL. Note that each user's tables are structured differently (i.e. I couldn't put all user data into one, super long table).

We currently store each user's data in a schema dedicated to that user but all schemas are in the same DB. The only way users can get to their data is through our application and it uses one user & password to access all schemas in the DB.

As we get more folks testing our system, I am starting to think more deeply about security. One thing I'm considering is dedicating a unique UID / PW for each application user and giving that UID access only to that user's schema. In addition, I would like to encrypt each user's data using a key specific to that user (it's been suggested to me that this protects data should a bug in our application accidentally give a user access to some other user's schema).

So, my question is this: can I encrypt a Google Cloud MySQL DB at the schema level and, if so, how? If not, is the only option to create a separate instance for each user? 

Thanks!

Ben

--
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/b66d1c40-6736-4730-9ca4-da863401c235n%40googlegroups.com.

[google-cloud-sql-discuss] Can I encrypt MySQL at the Schema / DB level?

We have developed a data matching application where each user can upload their data and use the features we provide. While it will change in the future, we are currently built on MySQL. Note that each user's tables are structured differently (i.e. I couldn't put all user data into one, super long table).

We currently store each user's data in a schema dedicated to that user but all schemas are in the same DB. The only way users can get to their data is through our application and it uses one user & password to access all schemas in the DB.

As we get more folks testing our system, I am starting to think more deeply about security. One thing I'm considering is dedicating a unique UID / PW for each application user and giving that UID access only to that user's schema. In addition, I would like to encrypt each user's data using a key specific to that user (it's been suggested to me that this protects data should a bug in our application accidentally give a user access to some other user's schema).

So, my question is this: can I encrypt a Google Cloud MySQL DB at the schema level and, if so, how? If not, is the only option to create a separate instance for each user? 

Thanks!

Ben

--
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/5fe08e1d-cb09-4058-b46c-4a2df0469132n%40googlegroups.com.

[google-cloud-sql-discuss] Re: Google Cloud SQL stuck at restart

There could be several reasons why your instance is stuck in a restart or suspended state. If you look here and here, it will provide you with some of the most common issues you might face.

It is also a good idea to access the Cloud SQL instance from the Cloud Shell with the gcloud debug flags to provide you with as much information as possible to resolve the issue.

Please note, do not share the output after using the debug flags unless you redact all identifiable information.

```

--log-http --verbosity=debug

```

On Wednesday, April 21, 2021 at 10:20:28 AM UTC+2 dayamo...@gmail.com wrote:

My cloud sql instance is stuck in Restart sate for a very long time. In the operations pane, the status of the Restart is showing as pending.

--
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/62f5900b-0199-4972-bfb3-164c837594den%40googlegroups.com.

[google-cloud-sql-discuss] Re: Clous SQL MySQL Query Optimization

According to the documentation:

"Cloud SQL automatically ensures your databases are reliable, secure, and scalable so that your business continues to run without disruption. Cloud SQL automates all your backups, replication, encryption patches, and capacity increases—while ensuring greater than 99.95% availability, anywhere in the world."

This means the underlying Operating System will receive patches and security updates, will be scaled as required, the ability to restore your instance etc.

What you run inside the database will be the responsibility of the user. However, GCP provides tools that a user can leverage to optimise queries such as slow query flags or general database configuration. 

On Tuesday, April 20, 2021 at 10:17:25 AM UTC+2 andrew choi wrote:

Hi, 

When it says fully-managed database service, does it mean Google Cloud SQL also provide basic optimization of the database such query performance improvement?

Thank you 

--
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/d4a42d09-c86c-434f-903f-79be5e1ec2c7n%40googlegroups.com.

[google-cloud-sql-discuss] Re: Details of Calculator Cost

If you scroll to the bottom of the cost calculator page, it will tell you that the costs are estimates only. The $67.91 will be for the Cloud SQL instance running 24 hours a day and seven days a week for a month.

The cost you have calculated yourself is for 160 hours a month, about 5 hours a day. The actual price might be higher or lower depending on what you are trying to implement.

On Wednesday, April 21, 2021 at 10:20:28 AM UTC+2 muh.mu...@gmail.com wrote:

I tried to use the product calculator here

https://cloud.google.com/products/calculator/#id=f5b35a8e-b8a3-4412-a9f3-af00bfb113c6

and got a result $67.91 in Cloud SQL

anyone knows how this result comes up?

because if I refer to this page 

https://cloud.google.com/sql/pricing

it should be $52.28
===================
(db-g1-small, $0.0455)
8/5 hour (160h/month)
$0.0455 x 160 =  $7.28

$0.090 per GB/month for HDD storage capacity
500gb/month
$0.090 x 500 = $45

The grand total will be $52.28

--
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/332948f5-5df9-4b01-932a-121ee8aab8fan%40googlegroups.com.

[google-cloud-sql-discuss] Re: Auditing Connection to Database

Hi, 

I would like to suggest you explore the Audit logs for more connection information on Cloud SQL. However, as per the Feature Request, currently the only way to audit new connections to the database is when the connections are performed via the Cloud SQL admin API. 

Hope it helps.

On Wednesday, April 7, 2021 at 11:45:36 AM UTC-4 stevanus hendry wrote:

Hello, I need an audit connection to the database PostgreSQL on cloud SQL, but  I did not implement log_connections. How can I get connection history beside log_connections?

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/93bb160e-0ff6-4365-808c-090963fbab95n%40googlegroups.com.

[google-cloud-sql-discuss] Re: select command denied for root

Hello,

Thank you for reporting the issue. 

Which connection method are you using?

Can you please provide steps to reproduce the issue?

On Friday, 16 April 2021 at 09:50:33 UTC+2 chravi...@gmail.com wrote:

I am facing a very strange issue. 

I created a google cloud instnace which also created the root user to import all databased from external source.

 However, when i try to select any table i get the error

https://prnt.sc/11hl93h

when i login as root and use the show grants command, i get 

https://prnt.sc/11hl6ul

The user root is shown in the users section of the cloudSQL

https://prnt.sc/11hla6o

Google cloud documentation is useless and wrong 

https://prnt.sc/11hlbs0

Did any one have this issue with cloudSQL? If yes, how did you resolve it.

Thanks and Regards

Ravi Kumar

--
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/17bbf318-4c60-4cf1-98b6-fd988c34682an%40googlegroups.com.

[google-cloud-sql-discuss] Re: Guide me how to install sql

Hello, 

Please follow the official documetation about how to create and connect to a MySQL instance and perform basic SQL operations using the Google Cloud Console and a client: 

Quickstart for Cloud SQL for MySQL [1]

You can find the cost of Google Cloud SQL here [2]

-----------------------

[1]. https://cloud.google.com/sql/docs/mysql/quickstart

[2]. https://cloud.google.com/sql/pricing

On Monday, April 12, 2021 at 11:24:38 AM UTC+2 HOPE VISION SERVICE wrote:

Hello,

    Please guide me . How to install sql database. Before i would like to know, it is free of cost or cost applicable. how much it is ?

On Thursday, June 25, 2020 at 3:03:08 AM UTC+5:30 Elliott (Google Cloud Platform Support) wrote:

Hello,

This forum is for Google Cloud SQL. It looks like you need help setting up a Virtual Machine for your Web application. If you can provide more context on how to make it run, maybe we can find a better place to answer your questions.

--
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/62a8d267-07ff-4ecd-a3fa-88dbb41643efn%40googlegroups.com.

[google-cloud-sql-discuss] Re: SQL cost and installation

Hello, 

You can find more information about Google Cloud SQL here [1].

Also, please check PHP 7 Runtime Environment on Google Cloud App Engine Standard [2]. 

These services are charged [3] [4]. 

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

[2]. https://cloud.google.com/appengine/docs/standard/php7/runtime

[3]. https://cloud.google.com/sql/pricing

[4]. https://cloud.google.com/appengine/pricing

On Monday, April 12, 2021 at 11:24:42 AM UTC+2 HOPE VISION SERVICE wrote:

Hi,

    I would like to know, how to install SQL and php. Suppose If I use sql and php. is it free of cost or not free of cost to use.

please guide me how to install Sql and php. 

Regards

Harish

--
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/1ef3f48c-7e9a-43f1-bf83-80fd4e0a2bb6n%40googlegroups.com.

[google-cloud-sql-discuss] Details of Calculator Price

I tried to use product calculator in here

https://cloud.google.com/products/calculator/#id=f5b35a8e-b8a3-4412-a9f3-af00bfb113c6

and got result $67.91 in Cloud SQL

can I know the details of this result?
because if I refere to this page 

https://cloud.google.com/sql/pricing

it should be $52.28

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

(db-g1-small, $0.0455)
8/5 hour (160h/month)
$0.0455 x 160 =  $7.28

$0.090 per GB/month for HDD storage capacity
500gb/month 
$0.090 = $45

The grand total will be $52.28

--
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/0d064dad-4847-490c-9315-401780cd1321n%40googlegroups.com.

[google-cloud-sql-discuss] Details of Calculator Cost

I tried to use the product calculator here

https://cloud.google.com/products/calculator/#id=f5b35a8e-b8a3-4412-a9f3-af00bfb113c6

and got a result $67.91 in Cloud SQL

anyone knows how this result comes up?

because if I refer to this page 

https://cloud.google.com/sql/pricing

it should be $52.28
===================
(db-g1-small, $0.0455)
8/5 hour (160h/month)
$0.0455 x 160 =  $7.28

$0.090 per GB/month for HDD storage capacity
500gb/month
$0.090 x 500 = $45

The grand total will be $52.28

--
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/8b0ea3be-7aed-425a-a7dd-adbe5926cbe6n%40googlegroups.com.

[google-cloud-sql-discuss] Google Cloud SQL stuck at restart

My cloud sql instance is stuck in Restart sate for a very long time. In the operations pane, the status of the Restart is showing as pending.

--
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/d8b14a5c-4382-4d5f-8e99-30358762440bn%40googlegroups.com.

[google-cloud-sql-discuss] Clous SQL MySQL Query Optimization

Hi, 

When it says fully-managed database service, does it mean Google Cloud SQL also provide basic optimization of the database such query performance improvement?

Thank you 

--
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/649d9e81-72f4-4c21-bbd2-b95692c4955fn%40googlegroups.com.

[google-cloud-sql-discuss] Re: Audit Log not generating DML statement logs for Cloud-SQL

Hello,

I see you have asked this on Stackoverflow and gotten a response from us. Please continue the interaction within the Stackoverflow post.

On Sunday, April 18, 2021 at 9:19:16 AM UTC-4 Bharath wrote:

I am trying to display audit logs for Cloud-SQL in the stack-driver-console. I have already enabled audit-log for Cloud-SQL in IAM. 

I connect to mysql or postgres databases in Cloud-SQL and when I connect these audit logs are displayed in the console.

request: { @type: "type.googleapis.com/google.cloud.sql.v1beta4.SqlInstancesGetRequest" instance: "testpostgres"

But after this if i perform any operation in that particular database like SELECT or INSERT or DELETE, there is no audit-log (data-access) generated for both mysql and postgres. In mysql instance I have set the following database flags

audit_log ON (this is in beta version)

For mysql if i add 1 more flag **general_log** I am able to get those DML statements but they come under a different log **cloudsql.googleapis.com%2Fmysql-general.log** and don't come under audit-logs

Similarly for post-gres these statements come under a different log:

**cloudsql.googleapis.com%2Fpostgres.log**

I am new to this Cloud-SQL so not aware of the logging implemented there. Why no audit logs are generated when any DML is done for the particular database in that Cloud-SQL instance and should I set any other flag for this purpose? Can anyone please help?

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/50603627-fb95-4c0b-a54b-de40a4b3dacbn%40googlegroups.com.

[google-cloud-sql-discuss] Re: how to configure replication(read-replica) for MS-SQL in Cloud SQL?

Hello Bharath, 

It is possible to create a read replica for a MySQL instance as well, as detailed on the "Replication in Cloud SQL" page. For the precise details on creating such a read replica, you may refer to the "Creating Read Replicas" documentation page. 

On Thursday, 15 April 2021 at 11:48:19 UTC-4 Bharath wrote:

I am exploring Cloud SQL and the various flavours(mysql,postgressql,MS-SQL). I am able to create read replicas for my-sql and postgres-sql , but i don't find that option for MS-SQL. Is it possible to create read replica of MS-SQL Cloud Database created in Cloud-SQL without using any 3rd party support?

Note: Also i find the documentation is the ms-sql read replica pages.

FYI the screenshot i got from the Cloud-SQL options:

Thanks

Bharath

--
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/b5331e97-6bf5-42c7-b01c-a6acc31e02edn%40googlegroups.com.

[google-cloud-sql-discuss] Audit Log not generating DML statement logs for Cloud-SQL

I am trying to display audit logs for Cloud-SQL in the stack-driver-console. I have already enabled audit-log for Cloud-SQL in IAM. 

I connect to mysql or postgres databases in Cloud-SQL and when I connect these audit logs are displayed in the console.

request: { @type: "type.googleapis.com/google.cloud.sql.v1beta4.SqlInstancesGetRequest" instance: "testpostgres"

But after this if i perform any operation in that particular database like SELECT or INSERT or DELETE, there is no audit-log (data-access) generated for both mysql and postgres. In mysql instance I have set the following database flags

audit_log ON (this is in beta version)

For mysql if i add 1 more flag **general_log** I am able to get those DML statements but they come under a different log **cloudsql.googleapis.com%2Fmysql-general.log** and don't come under audit-logs

Similarly for post-gres these statements come under a different log:

**cloudsql.googleapis.com%2Fpostgres.log**

I am new to this Cloud-SQL so not aware of the logging implemented there. Why no audit logs are generated when any DML is done for the particular database in that Cloud-SQL instance and should I set any other flag for this purpose? Can anyone please help?

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/67b7ba4e-36dc-4f9c-b14f-fb260ae5bc35n%40googlegroups.com.

[google-cloud-sql-discuss] Re: SQL connection time out error

thank you

On Friday, April 16, 2021 at 11:06:45 AM UTC-4 wushawn wrote:

There are many reasons why a connection attempt might not succeed. Network communication is never guaranteed, and the database might be temporarily unable to respond. Make sure your application handles broken or unsuccessful connections gracefully. I recommend you to check the logs to understand the connection timeout error.

On Thursday, April 15, 2021 at 6:39:37 PM UTC-4 kumar.pa...@gmail.com wrote:

Why do I get this error on GCP:

SQL Server PROD connection Time out. I appreciate your answers 

--
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/47c2d8a9-ec49-4ccc-b544-940cfa59147fn%40googlegroups.com.

[google-cloud-sql-discuss] Re: SQL connection time out error

There are many reasons why a connection attempt might not succeed. Network communication is never guaranteed, and the database might be temporarily unable to respond. Make sure your application handles broken or unsuccessful connections gracefully. I recommend you to check the logs to understand the connection timeout error.

On Thursday, April 15, 2021 at 6:39:37 PM UTC-4 kumar.pa...@gmail.com wrote:

Why do I get this error on GCP:

SQL Server PROD connection Time out. I appreciate your answers 

--
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/59c76d49-aa97-4b19-aa72-6ed66815c630n%40googlegroups.com.

[google-cloud-sql-discuss] select command denied for root

I am facing a very strange issue. 

I created a google cloud instnace which also created the root user to import all databased from external source.

 However, when i try to select any table i get the error

https://prnt.sc/11hl93h

when i login as root and use the show grants command, i get 

https://prnt.sc/11hl6ul

The user root is shown in the users section of the cloudSQL

https://prnt.sc/11hla6o

Google cloud documentation is useless and wrong 

https://prnt.sc/11hlbs0

Did any one have this issue with cloudSQL? If yes, how did you resolve it.

Thanks and Regards

Ravi Kumar

--
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/0df3b5f9-92ca-4d90-8390-f4fcac2e3957n%40googlegroups.com.

[google-cloud-sql-discuss] JDBC: Apps Script and Google MySQL : Exception: You do not have permission to call Jdbc.getCloudSqlConnection

I get the following error when I attempt to run this function within google sheets: 

Exception: You do not have permission to call Jdbc.getCloudSqlConnection

any idea on how to fix this?

 

var connectionName = 'cosmic-tenure-310821:us-central1:propertydata'; 

var rootPwd = "password"; 

var user = "root"; var userPwd = 'password'; v

ar db = 'propertydata'; v

ar root = 'root'; v

ar instanceUrl = "jdbc:google:mysql://" + connectionName; var dbUrl = instanceUrl + "/" + db; f

unction createTable() 

 var conn = Jdbc.getCloudSqlConnection(dbUrl, user, userPwd); conn.createStatement().execute('CREATE TABLE myProperties(APN INT, APNObject MEDIUMBLOB)'); 

}

--
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/332613b2-266a-433f-a0da-78a1bbc90989n%40googlegroups.com.

[google-cloud-sql-discuss] SQL connection time out error

Why do I get this error on GCP:

SQL Server PROD connection Time out. I appreciate your answers 

--
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/ce154f05-a55f-430f-8dbc-b4cedfd4b5a5n%40googlegroups.com.

[google-cloud-sql-discuss] how to configure replication(read-replica) for MS-SQL in Cloud SQL?

I am exploring Cloud SQL and the various flavours(mysql,postgressql,MS-SQL). I am able to create read replicas for my-sql and postgres-sql , but i don't find that option for MS-SQL. Is it possible to create read replica of MS-SQL Cloud Database created in Cloud-SQL without using any 3rd party support?

Note: Also i find the documentation is the ms-sql read replica pages.

FYI the screenshot i got from the Cloud-SQL options:

Thanks

Bharath

--
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/eb54e575-8df8-4143-8323-7f984da8d7e6n%40googlegroups.com.

[google-cloud-sql-discuss] Re: Consistent "Segmentation fault" error in logs when running a query

After prolonged testing, I have an update: to completely stop segfaults, Query Insights must be disabled after all. Merely disabling application tags makes them less frequent, but doesn't prevent them entirely.

On Thursday, April 15, 2021 at 2:39:51 AM UTC+12 e...@contractbook.dk wrote:

Hi

> Would you be able to confirm if you are still able to see the segmentation fault errors? 

Yes, I confirm this. The last one per our logs happened today at 2021-04-13 08:11:32.469 UTC. The segmentation errors are not extremely common (due to low traffic on staging environment), but happen every day, once or twice. This may become a deal breaker should be plan to move our production DB to Google Cloud though.

> does the query involve a LEFT JOIN?

The query definition itself has two JOINs, although not LEFT JOINs. However, one of the joined relations is a view that is defined to have LEFT JOINs in it.

Noted on the SO question. I am not sure what to take from it though...

Noted on the issue tracker too. I'll gather up the info I have so far and will publish there. Thank you!

On Monday, April 12, 2021 at 12:24:55 PM UTC+3 jli...@google.com wrote:

Hello, 

Would you be able to confirm if you are still able to see the segmentation fault errors? If so, would you be able to please provide the most recent timestamp of the occurrence. 

Also, would you be able to provide a little more details regarding the query? As per Andrew's question, does the query involve a LEFT JOIN? According to the post presented here [1], this may be due to a PostgreSQL bug. Would you be able to verify this and get back to use with this information? 

Better yet, I would suggest you bring this issue up via public issue tracker [2], as this will allow for a more in depth investigation into the segmentation fault; at the same time bring the issue closer to the Cloud SQL team for further inspection.

[1] https://stackoverflow.com/questions/55585276/postgres-crashes-with-segmentation-fault-when-using-left-join

[2] issuetracker.google.com

On Tuesday, March 30, 2021 at 1:10:32 PM UTC-4 Andrew K. wrote:

Does this query involve either a LEFT JOIN or aggregate functions? We have a very similar issue with Cloud SQL Postgres 12.5, with four different queries causing segmentation faults, and these are the only similarities between then. So far we were not able to reproduce the segfaults on a local PG instance running the same DB and queries, and unfortunately it's not possible to attach a debugger to Cloud SQL (as far as we know).

On Tuesday, March 30, 2021 at 3:23:04 AM UTC+13 e...@contractbook.dk wrote:

We're seeing a "Segmentation fault" error in logs for our staging environment, caused by a single specific DB query.

I am unable to replicate the problem consistently by running the same query manually, but we see the issue in logs basically every day now.

Our environment is: PostgreSQL 13.1, the DB tier is "db-custom-1-3840".

In the 1st half of February, we were seeing "Segmentation fault" in relation to another DB query & different DB instance. That issue somehow got self-resolved around Feb 15.

I'd love to provide more info to diagnose this – is there any other info I could provide that would help solve this case? Otherwise, would it be possible for a Google Cloud SQL engineer look into this for us?

--
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/8450f075-7305-4669-9b0b-bc1e920db737n%40googlegroups.com.

[google-cloud-sql-discuss] Re: Consistent "Segmentation fault" error in logs when running a query

Posted a comment to an issue with a similar name here: https://issuetracker.google.com/issues/184283279

On Monday, April 12, 2021 at 12:24:55 PM UTC+3 jli...@google.com wrote:

Hello, 

Would you be able to confirm if you are still able to see the segmentation fault errors? If so, would you be able to please provide the most recent timestamp of the occurrence. 

Also, would you be able to provide a little more details regarding the query? As per Andrew's question, does the query involve a LEFT JOIN? According to the post presented here [1], this may be due to a PostgreSQL bug. Would you be able to verify this and get back to use with this information? 

Better yet, I would suggest you bring this issue up via public issue tracker [2], as this will allow for a more in depth investigation into the segmentation fault; at the same time bring the issue closer to the Cloud SQL team for further inspection.

[1] https://stackoverflow.com/questions/55585276/postgres-crashes-with-segmentation-fault-when-using-left-join

[2] issuetracker.google.com

On Tuesday, March 30, 2021 at 1:10:32 PM UTC-4 Andrew K. wrote:

Does this query involve either a LEFT JOIN or aggregate functions? We have a very similar issue with Cloud SQL Postgres 12.5, with four different queries causing segmentation faults, and these are the only similarities between then. So far we were not able to reproduce the segfaults on a local PG instance running the same DB and queries, and unfortunately it's not possible to attach a debugger to Cloud SQL (as far as we know).

On Tuesday, March 30, 2021 at 3:23:04 AM UTC+13 e...@contractbook.dk wrote:

We're seeing a "Segmentation fault" error in logs for our staging environment, caused by a single specific DB query.

I am unable to replicate the problem consistently by running the same query manually, but we see the issue in logs basically every day now.

Our environment is: PostgreSQL 13.1, the DB tier is "db-custom-1-3840".

In the 1st half of February, we were seeing "Segmentation fault" in relation to another DB query & different DB instance. That issue somehow got self-resolved around Feb 15.

I'd love to provide more info to diagnose this – is there any other info I could provide that would help solve this case? Otherwise, would it be possible for a Google Cloud SQL engineer look into this for us?

--
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/f06f0b77-bdfc-4eb6-b0c5-b663c93170c8n%40googlegroups.com.

[google-cloud-sql-discuss] Re: Consistent "Segmentation fault" error in logs when running a query

Hi

> Would you be able to confirm if you are still able to see the segmentation fault errors? 

Yes, I confirm this. The last one per our logs happened today at 2021-04-13 08:11:32.469 UTC. The segmentation errors are not extremely common (due to low traffic on staging environment), but happen every day, once or twice. This may become a deal breaker should be plan to move our production DB to Google Cloud though.

> does the query involve a LEFT JOIN?

The query definition itself has two JOINs, although not LEFT JOINs. However, one of the joined relations is a view that is defined to have LEFT JOINs in it.

Noted on the SO question. I am not sure what to take from it though...

Noted on the issue tracker too. I'll gather up the info I have so far and will publish there. Thank you!

On Monday, April 12, 2021 at 12:24:55 PM UTC+3 jli...@google.com wrote:

Hello, 

Would you be able to confirm if you are still able to see the segmentation fault errors? If so, would you be able to please provide the most recent timestamp of the occurrence. 

Also, would you be able to provide a little more details regarding the query? As per Andrew's question, does the query involve a LEFT JOIN? According to the post presented here [1], this may be due to a PostgreSQL bug. Would you be able to verify this and get back to use with this information? 

Better yet, I would suggest you bring this issue up via public issue tracker [2], as this will allow for a more in depth investigation into the segmentation fault; at the same time bring the issue closer to the Cloud SQL team for further inspection.

[1] https://stackoverflow.com/questions/55585276/postgres-crashes-with-segmentation-fault-when-using-left-join

[2] issuetracker.google.com

On Tuesday, March 30, 2021 at 1:10:32 PM UTC-4 Andrew K. wrote:

Does this query involve either a LEFT JOIN or aggregate functions? We have a very similar issue with Cloud SQL Postgres 12.5, with four different queries causing segmentation faults, and these are the only similarities between then. So far we were not able to reproduce the segfaults on a local PG instance running the same DB and queries, and unfortunately it's not possible to attach a debugger to Cloud SQL (as far as we know).

On Tuesday, March 30, 2021 at 3:23:04 AM UTC+13 e...@contractbook.dk wrote:

We're seeing a "Segmentation fault" error in logs for our staging environment, caused by a single specific DB query.

I am unable to replicate the problem consistently by running the same query manually, but we see the issue in logs basically every day now.

Our environment is: PostgreSQL 13.1, the DB tier is "db-custom-1-3840".

In the 1st half of February, we were seeing "Segmentation fault" in relation to another DB query & different DB instance. That issue somehow got self-resolved around Feb 15.

I'd love to provide more info to diagnose this – is there any other info I could provide that would help solve this case? Otherwise, would it be possible for a Google Cloud SQL engineer look into this for us?

--
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/039fb20d-9bcd-49b5-92fd-0639853beec7n%40googlegroups.com.

Re: [google-cloud-sql-discuss] required cost

Refer - 
https://cloud.google.com/products/calculator for pricing details.

You can sign up for free trial post which you will be fairly charged.

--

Apologies for any spelling errors - sent from my phone.

On Mon, 12 Apr, 2021, 2:54 pm HOPE VISION SERVICE, <hopevisionservice@gmail.com> wrote:

hi,

     If i am using google cloud sql and php in my google domain. please tell me how much it cost or cost is applicable or not ?

if the charges is applicable means, what is the lowest price to use sql.

but my requirement is below 1 gb.

please reply 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/e8df9c5d-d9b1-4a5a-b4d9-a1c6bcc4d1f7n%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/CAELv%3DOSF0GGFp24vsXJSC_TiBJ-SBjqRX0yCF4Q9K8UJAH7Q_g%40mail.gmail.com.

[google-cloud-sql-discuss] Re: Consistent "Segmentation fault" error in logs when running a query

Good news: I can confirm that disabling Query Insights on our production instance has made segfaults stop completely. What's more interesting is that we've re-enabled it with application tags disabled, and so far no segfaults either.

On Monday, April 12, 2021 at 9:50:40 PM UTC+12 Andrew K. wrote:

From our side, we can definitely confirm they are still occurring. The most recent occurrence for us is less than 20 minutes ago, 2021-04-12 09:25:38.469 UTC and we're seeing about 20 segfaults a day on our production instance.

Unfortunately, due to the inability to collect stack traces via Cloud SQL, there is not much we can do to debug further. The PG bug you have linked dates back to PG 9.6 and is unlikely to have gone unnoticed and not been fixed by PG 13 (we've verified that it happens for us both on PG 12 and 13). Considering that we have not been able to reproduce it locally so far, it could very well be isolated to Cloud SQL implementation of Postgres. Reporting it to PG won't help, since they will request stack traces we cannot collect.

There are a few threads on the Google issue tracker that suggest Query Insights may be responsible for segmentation faults. Since we have it enabled, I will try disabling it (if I can find out how to do that) and report back.

On Monday, April 12, 2021 at 9:24:55 PM UTC+12 jli...@google.com wrote:

Hello, 

Would you be able to confirm if you are still able to see the segmentation fault errors? If so, would you be able to please provide the most recent timestamp of the occurrence. 

Also, would you be able to provide a little more details regarding the query? As per Andrew's question, does the query involve a LEFT JOIN? According to the post presented here [1], this may be due to a PostgreSQL bug. Would you be able to verify this and get back to use with this information? 

Better yet, I would suggest you bring this issue up via public issue tracker [2], as this will allow for a more in depth investigation into the segmentation fault; at the same time bring the issue closer to the Cloud SQL team for further inspection.

[1] https://stackoverflow.com/questions/55585276/postgres-crashes-with-segmentation-fault-when-using-left-join

[2] issuetracker.google.com

On Tuesday, March 30, 2021 at 1:10:32 PM UTC-4 Andrew K. wrote:

Does this query involve either a LEFT JOIN or aggregate functions? We have a very similar issue with Cloud SQL Postgres 12.5, with four different queries causing segmentation faults, and these are the only similarities between then. So far we were not able to reproduce the segfaults on a local PG instance running the same DB and queries, and unfortunately it's not possible to attach a debugger to Cloud SQL (as far as we know).

On Tuesday, March 30, 2021 at 3:23:04 AM UTC+13 e...@contractbook.dk wrote:

We're seeing a "Segmentation fault" error in logs for our staging environment, caused by a single specific DB query.

I am unable to replicate the problem consistently by running the same query manually, but we see the issue in logs basically every day now.

Our environment is: PostgreSQL 13.1, the DB tier is "db-custom-1-3840".

In the 1st half of February, we were seeing "Segmentation fault" in relation to another DB query & different DB instance. That issue somehow got self-resolved around Feb 15.

I'd love to provide more info to diagnose this – is there any other info I could provide that would help solve this case? Otherwise, would it be possible for a Google Cloud SQL engineer look into this for us?

--
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/5291da48-6bf4-43a2-a63f-d6b8948f761en%40googlegroups.com.

[google-cloud-sql-discuss] Re: Consistent "Segmentation fault" error in logs when running a query

From our side, we can definitely confirm they are still occurring. The most recent occurrence for us is less than 20 minutes ago, 2021-04-12 09:25:38.469 UTC and we're seeing about 20 segfaults a day on our production instance.

Unfortunately, due to the inability to collect stack traces via Cloud SQL, there is not much we can do to debug further. The PG bug you have linked dates back to PG 9.6 and is unlikely to have gone unnoticed and not been fixed by PG 13 (we've verified that it happens for us both on PG 12 and 13). Considering that we have not been able to reproduce it locally so far, it could very well be isolated to Cloud SQL implementation of Postgres. Reporting it to PG won't help, since they will request stack traces we cannot collect.

There are a few threads on the Google issue tracker that suggest Query Insights may be responsible for segmentation faults. Since we have it enabled, I will try disabling it (if I can find out how to do that) and report back.

On Monday, April 12, 2021 at 9:24:55 PM UTC+12 jli...@google.com wrote:

Hello, 

Would you be able to confirm if you are still able to see the segmentation fault errors? If so, would you be able to please provide the most recent timestamp of the occurrence. 

Also, would you be able to provide a little more details regarding the query? As per Andrew's question, does the query involve a LEFT JOIN? According to the post presented here [1], this may be due to a PostgreSQL bug. Would you be able to verify this and get back to use with this information? 

Better yet, I would suggest you bring this issue up via public issue tracker [2], as this will allow for a more in depth investigation into the segmentation fault; at the same time bring the issue closer to the Cloud SQL team for further inspection.

[1] https://stackoverflow.com/questions/55585276/postgres-crashes-with-segmentation-fault-when-using-left-join

[2] issuetracker.google.com

On Tuesday, March 30, 2021 at 1:10:32 PM UTC-4 Andrew K. wrote:

Does this query involve either a LEFT JOIN or aggregate functions? We have a very similar issue with Cloud SQL Postgres 12.5, with four different queries causing segmentation faults, and these are the only similarities between then. So far we were not able to reproduce the segfaults on a local PG instance running the same DB and queries, and unfortunately it's not possible to attach a debugger to Cloud SQL (as far as we know).

On Tuesday, March 30, 2021 at 3:23:04 AM UTC+13 e...@contractbook.dk wrote:

We're seeing a "Segmentation fault" error in logs for our staging environment, caused by a single specific DB query.

I am unable to replicate the problem consistently by running the same query manually, but we see the issue in logs basically every day now.

Our environment is: PostgreSQL 13.1, the DB tier is "db-custom-1-3840".

In the 1st half of February, we were seeing "Segmentation fault" in relation to another DB query & different DB instance. That issue somehow got self-resolved around Feb 15.

I'd love to provide more info to diagnose this – is there any other info I could provide that would help solve this case? Otherwise, would it be possible for a Google Cloud SQL engineer look into this for us?

--
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/73d6496f-d92b-417c-a786-7a640b3e4ca6n%40googlegroups.com.

[google-cloud-sql-discuss] Re: DataStudio for MySQL 8.0

Hi,

Unfortunately, Data Studio cannot connect to Cloud MySQL 8.0 directly at the moment. However, there is a feature request with Cloud SQL product team on the issue. There is no guarantee of implementation or any ETA at this time. You may star these public issue trackers[1,2] to receive any update about this feature request in the future.

As a workaround, you may use the previous Cloud MySQL version or try the workarounds suggested in the aforementioned issue trackers. And in this stackoverflow issue[3], Salvi Pascual also provides a workaround for you to reference.

Please keep in mind that Data Studio is not owned by the Google Cloud Platform team, and if you need support in the future about Data Studio, you may contact the respective support team[4].

I hope that this makes things clearer for you. If you have any other questions or concerns about this case, It will be our pleasure to assist you further.

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

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

[3] https://stackoverflow.com/questions/58031175/cant-connect-google-datastudio-and-mysql-8

[4] https://sites.google.com/corp/google.com/datastudio/contact

On Thursday, April 8, 2021 at 6:16:17 PM UTC-4 pa...@classkick.com wrote:

Does DataStudio support MySQL 8.0 yet?  Documentation says no - just checking if that's up-to-date.  If not, any indication when to expect 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/21c8d8d6-34cf-46a3-b00e-fa83624c8d6fn%40googlegroups.com.

[google-cloud-sql-discuss] Re: Consistent "Segmentation fault" error in logs when running a query

Hello, 

Would you be able to confirm if you are still able to see the segmentation fault errors? If so, would you be able to please provide the most recent timestamp of the occurrence. 

Also, would you be able to provide a little more details regarding the query? As per Andrew's question, does the query involve a LEFT JOIN? According to the post presented here [1], this may be due to a PostgreSQL bug. Would you be able to verify this and get back to use with this information? 

Better yet, I would suggest you bring this issue up via public issue tracker [2], as this will allow for a more in depth investigation into the segmentation fault; at the same time bring the issue closer to the Cloud SQL team for further inspection.

[1] https://stackoverflow.com/questions/55585276/postgres-crashes-with-segmentation-fault-when-using-left-join

[2] issuetracker.google.com

On Tuesday, March 30, 2021 at 1:10:32 PM UTC-4 Andrew K. wrote:

Does this query involve either a LEFT JOIN or aggregate functions? We have a very similar issue with Cloud SQL Postgres 12.5, with four different queries causing segmentation faults, and these are the only similarities between then. So far we were not able to reproduce the segfaults on a local PG instance running the same DB and queries, and unfortunately it's not possible to attach a debugger to Cloud SQL (as far as we know).

On Tuesday, March 30, 2021 at 3:23:04 AM UTC+13 e...@contractbook.dk wrote:

We're seeing a "Segmentation fault" error in logs for our staging environment, caused by a single specific DB query.

I am unable to replicate the problem consistently by running the same query manually, but we see the issue in logs basically every day now.

Our environment is: PostgreSQL 13.1, the DB tier is "db-custom-1-3840".

In the 1st half of February, we were seeing "Segmentation fault" in relation to another DB query & different DB instance. That issue somehow got self-resolved around Feb 15.

I'd love to provide more info to diagnose this – is there any other info I could provide that would help solve this case? Otherwise, would it be possible for a Google Cloud SQL engineer look into this for us?

--
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/751b6f48-612f-490a-9b20-b628b39d6792n%40googlegroups.com.

[google-cloud-sql-discuss] Re: "Can't connect to MySQL server on 'localhost' ([Errno 111] Connection refused)")

Looking at some public forums [1][2] , I found some valid reasons why you may experiencing this error.  Mostly related to your MySQL server only listening the localhost interface or db user's privileges. 

[1]https://stackoverflow.com/a/1420862/7046224

[2]https://discuss.erpnext.com/t/cant-connect-to-mysql-server-on-u-local-host-error-111-connection-refused/41047/2

On Wednesday, April 7, 2021 at 11:45:36 AM UTC-4 stran...@gmail.com wrote:

My application is running.

I can run it and connect locally when point to ip on CloudSql

SQLALCHEMY_DATABASE_URI = "mysql+pymysql://{}:{}@{}/{}".format(db_user,db_pass,db_host,db_name)

When I change it and run it on server:

SQLALCHEMY_DATABASE_URI = "mysql+pymysql:///unix_socket=/{}/{}".format(db_user,db_pass,db_name,db_socket_dir,cloud_sql_connection_name)

I got:

sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'localhost' ([Errno 111] Connection refused)")

--
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/a76f2a49-ace1-43c1-bb1e-8e70d8b8f346n%40googlegroups.com.

[google-cloud-sql-discuss] strange queries

Hi

We're seeing in our MySQL instance logs, queries that don't belong to our code, and are trying to get data from our tables.

I think that we have an intromission, could you pls give some secuirty advice?

We're going to change all user passwords, none instance has public access enabled. 

The strange queries has this source: # User@Host: root[root] @ [cloudsqlproxy~]

Thanks in advance

Fabio

--
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/d1ffb60f-ee09-4738-92a7-9fe330f9faafn%40googlegroups.com.

[google-cloud-sql-discuss] please reply

hi,

     If i am using google cloud sql and php in my google domain. please tell me how much it cost or cost is applicable or not ?

if the charges is applicable means, what is the lowest price to use sql.

but my requirement is below 1 gb.

please reply 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/13137844-3d1a-4af0-966b-fb3c85972fden%40googlegroups.com.

[google-cloud-sql-discuss] required cost

hi,

     If i am using google cloud sql and php in my google domain. please tell me how much it cost or cost is applicable or not ?

if the charges is applicable means, what is the lowest price to use sql.

but my requirement is below 1 gb.

please reply 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/e8df9c5d-d9b1-4a5a-b4d9-a1c6bcc4d1f7n%40googlegroups.com.

[google-cloud-sql-discuss] SQL cost and installation

Hi,

    I would like to know, how to install SQL and php. Suppose If I use sql and php. is it free of cost or not free of cost to use.

please guide me how to install Sql and php. 

Regards

Harish

--
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/3aafd629-c8d4-40e8-adf0-9305ff50daf8n%40googlegroups.com.

[google-cloud-sql-discuss] Guide me how to install sql

Hello,

    Please guide me . How to install sql database. Before i would like to know, it is free of cost or cost applicable. how much it is ?

On Thursday, June 25, 2020 at 3:03:08 AM UTC+5:30 Elliott (Google Cloud Platform Support) wrote:

Hello,

This forum is for Google Cloud SQL. It looks like you need help setting up a Virtual Machine for your Web application. If you can provide more context on how to make it run, maybe we can find a better place to answer your questions.

--
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/45d18806-9f10-414c-a84f-ceee3457ed23n%40googlegroups.com.

[google-cloud-sql-discuss] DataStudio for MySQL 8.0

Does DataStudio support MySQL 8.0 yet?  Documentation says no - just checking if that's up-to-date.  If not, any indication when to expect 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/18e0401b-9e54-4f79-9f9b-a28d549c7d24n%40googlegroups.com.

[google-cloud-sql-discuss] Re: Failover operation in progress. This may take a few minutes. While this operation is running, you may continue to view information about the instance.

Hello,

Thank you for reaching out for help with this issue.

I do think contacting the Google Cloud Platform Support [1] would be better suited for your needs in this case. Google Groups Forums posts are for educational purposes and I think your issue would do well to have a member of the support community help you look into this issue and troubleshoot. There is also active members of the Google Cloud Platform Support Community that monitor Stack Overflow for issues similar to yours. Goodluck in assessing and resolving this issue

Kind Regards,

Alfio 

[1]: https://cloud.google.com/support-hub/

On Wednesday, April 7, 2021 at 2:39:20 PM UTC-4 jean...@gmail.com wrote:

Hello, 

This morning during a CloudSQL instance resize, somethig went wrong.. 

After some hours waiting, current instance is unreacheable and with an info "Failover operation in progress. This may take a few minutes. While this operation is running, you may continue to view information about the instance."

• Apr 7, 2021, 2:06:04 PM Failover Failover operation in progress
• Apr 7, 2021, 1:34:29 PM Failover  An unknown error occurred
• Apr 7, 2021, 1:02:39 PM Failover  An unknown error occurred
• Apr 7, 2021, 12:30:54 PM Failover  An unknown error occurred
• Apr 7, 2021, 11:59:04 AM Failover  An unknown error occurred
• Apr 7, 2021, 11:27:19 AM Failover  An unknown error occurred
• Apr 7, 2021, 10:55:28 AM Failover  An unknown error occurred
• Apr 7, 2021, 10:23:44 AM Failover  An unknown error occurred
• Apr 7, 2021, 9:48:44 AM Update  An unknown error occurred

Cloud SQL, Postgres 11, configure to be HA.

What procedure should I take now?

--
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/1da52183-11da-4198-ad19-c426dc9d2f2dn%40googlegroups.com.

[google-cloud-sql-discuss] Failover operation in progress. This may take a few minutes. While this operation is running, you may continue to view information about the instance.

Hello, 

This morning during a CloudSQL instance resize, somethig went wrong.. 

After some hours waiting, current instance is unreacheable and with an info "Failover operation in progress. This may take a few minutes. While this operation is running, you may continue to view information about the instance."

• Apr 7, 2021, 2:06:04 PM Failover Failover operation in progress
• Apr 7, 2021, 1:34:29 PM Failover  An unknown error occurred
• Apr 7, 2021, 1:02:39 PM Failover  An unknown error occurred
• Apr 7, 2021, 12:30:54 PM Failover  An unknown error occurred
• Apr 7, 2021, 11:59:04 AM Failover  An unknown error occurred
• Apr 7, 2021, 11:27:19 AM Failover  An unknown error occurred
• Apr 7, 2021, 10:55:28 AM Failover  An unknown error occurred
• Apr 7, 2021, 10:23:44 AM Failover  An unknown error occurred
• Apr 7, 2021, 9:48:44 AM Update  An unknown error occurred

Cloud SQL, Postgres 11, configure to be HA.

What procedure should I take now?

--
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/df7bac95-43af-4a85-a625-fb0e9755698fn%40googlegroups.com.

[google-cloud-sql-discuss] Re: Can't Add Storage Capacity of PostgreSQL Cloud SQL

How are you adding the storage? Are you using the `gcloud` CLI or the GCP Console? If you are following specific documentation, can you share it here and I am more than happy to advise you?

If you are using the `gcloud` CLI it might be failing silently so to help identify what might be happening. By adding some debug switches to the command, the output should provide more detailed information about what is happening.

```

$ gcloud sql instances patch <instance-name> --storage-size=250 --log-http --verbosity=debug

```

On Thursday, April 1, 2021 at 5:17:58 PM UTC+2 fredri...@gmail.com wrote:

I experienced the same issue. For me the trick was to do it with the gcloud cli instead. That worked as a charm:
gcloud sql instances patch <instance-name> --storage-size=250

Good luck!

On Monday, 29 March 2021 at 11:45:17 UTC+1 muhamma...@qasir.id wrote:

Hi,

When I try to add storage capacity of my PostgreSQL instance from 200 GB to 250 GB, I don't get any error message. But, storage capacity of my instance not change from 200 GB to 250 GB. Any one could help me please?. Thank you

--
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/d8d7175b-30f3-4bfc-a91e-6d0f31e5c8a1n%40googlegroups.com.

[google-cloud-sql-discuss] Auditing Connection to Database

Hello, I need an audit connection to the database PostgreSQL on cloud SQL, but  I did not implement log_connections. How can I get connection history beside log_connections?

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/e5016919-5798-4cd0-9b15-955f5eba2751n%40googlegroups.com.

[google-cloud-sql-discuss] "Can't connect to MySQL server on 'localhost' ([Errno 111] Connection refused)")

My application is running.

I can run it and connect locally when point to ip on CloudSql

SQLALCHEMY_DATABASE_URI = "mysql+pymysql://{}:{}@{}/{}".format(db_user,db_pass,db_host,db_name)

When I change it and run it on server:

SQLALCHEMY_DATABASE_URI = "mysql+pymysql:///unix_socket=/{}/{}".format(db_user,db_pass,db_name,db_socket_dir,cloud_sql_connection_name)

I got:

sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on 'localhost' ([Errno 111] Connection refused)")

--
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/8442cdee-54b0-4089-a333-30066eb41d82n%40googlegroups.com.