[google-cloud-sql-discuss] Re: CloudIAP with CloudSQL/Redis and Private Connect

As indicated on this IAP Overview documentation[1], IAP may be used with applications running on App Engine standard environment, App Engine flexible environment, Compute Engine, and GKE. The Cloud IAP cannot be configured with CloudSQL or Redis at the moment. A feature request was submitted with the IAP team for this implementation but there is no ETA for such implementations at this time. 

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

--
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/f5af6da6-2c4f-4a2d-a6eb-92818914ef88%40googlegroups.com.

[google-cloud-sql-discuss] CloudIAP with CloudSQL/Redis and Private Connect

Is it possible to configure Identity-aware proxy with redis and cloudSQL that are configured with private IPs/Private Connection?

--
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/ba49b857-ef10-42f1-b023-4d1ab8f166a3%40googlegroups.com.

[google-cloud-sql-discuss] Re: MySQL 5.8

Hi Jackson, 

This discussion group is oriented more towards general opinions, trends, and issues of general nature touching App Engine. For information benefiting your research paper on Cloud SQL related subjects, 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/e5f158ca-c9e7-41ec-bd4a-44a8253ad984%40googlegroups.com.

[google-cloud-sql-discuss] Re: MySQL 5.8

i am doing research for my FYP for my university, i am doing my research paper work on this, if you want to help me, get in touch with me.   

On Wednesday, 11 December 2019 22:50:40 UTC+5, Euan Mapham wrote:

Hi, 

I am just wondering if there are any plans for best watches under 10000 for cloud-sql to implement MySQL 5.8? expert watch man I do see that RDS supports MySQL 5.8 and was wondering anyone knows whether it is on the roadmap for cloud-sql?

Thanks,

Euan

--
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/ced358e3-711e-4f0d-a783-5fe8bbfdffd1%40googlegroups.com.

[google-cloud-sql-discuss] Re: MYSQL Read replica

Hello,

You will see this error occasionally. When the main instance is restarted, connections might be routed to your replica and you will get this message for write requests. We recommend that you implement error handling strategy like exponential backoff to reduce the amount of errors when this happens.

--
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/6e9907a8-c5f0-42b2-84b7-4332cd5d2bdd%40googlegroups.com.

[google-cloud-sql-discuss] Re: error: The MySQL server is running with the --read-only option so it cannot execute this statement

Hi,

You might want to consider using High Availability configuration, as this will ensure that all writes made to the primary instance are also made to the standby instance. This option will reduce downtime and your data continues to be available to client applications during maintenance time.

Another option to minimize the impact of downtime would be to set a Preferred Maintenance Window, as it will allow you to set a specific time and day to control the timing of maintenance.

--
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/9de46535-b049-4792-ac5e-7ea2499ae714%40googlegroups.com.

[google-cloud-sql-discuss] error: The MySQL server is running with the --read-only option so it cannot execute this statement

Hi, I have an issue with GCP Mysql. I have one master instance with 1 read replica. sometimes when there is maintenance operation on the server some write queries are routed to the read replica instance and therefore I get the following error: The MySQL server is running with the --read-only option so it cannot execute this statement. How should I handle this situation? thx

--
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/bf52ee4e-0a38-4ebd-bf62-9dc224020461%40googlegroups.com.

[google-cloud-sql-discuss] MYSQL Read replica

Hi,

I have an issue with GCP Mysql.

I have one master instance with 1 read replica. sometimes when there is maintenance operation on the server some write queries are routed to the read replica instance and therefore I get the following error: The MySQL server is running with the --read-only option so it cannot execute this statement.

How should I handle this situation?

there is an option to route to replica only read queries? thx

--
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/30476b0d-c09a-416f-9b73-f1688370f55d%40googlegroups.com.

[google-cloud-sql-discuss] Re: AUTOMATING Export and Import Of tables For CLOUD SQL postgresql database

I'm glad you were able to work it out and thanks for sharing your solution as this can be useful for other users who are looking to accomplish such tasks.

--
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/9e84bd81-138f-4279-b2f0-3b0e98bb9450%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cannot delete created role (Postgres 11)

I am not exactly clear about your last message. Are you suggesting that you would like to be granted the SuperUser Role? If that is what you mean, sadly, that is not available at this time. Otherwise, please let me know by clarifying the details shared. 

As you already know, it is expected behavior that Cloud SQL for PostgreSQL restricts the SuperUser access. This is not available for Customers in general. If you have particular requests or changes that you would like implemented, you could always submit a Feature request[1] using the issue tracker link[2]. Please note however, that such feature requests are subject to evaluation by the CloudSQL team and have no ETA for implementation. 

[1]https://cloud.google.com/support/docs/issue-trackers#feature_requests

[2]https://issuetracker.google.com/issues/new

--
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/df6ecb6d-0d4a-423a-83db-15c0bd7b1a96%40googlegroups.com.

[google-cloud-sql-discuss] Re: AUTOMATING Export and Import Of tables For CLOUD SQL postgresql database

Hi Aref,

Thank you so much for this reply. I apologize for the late feedback. Ended up creating a VM in Compute Engine, creating a network route to my On Prem Database and then another to the CloudSQL postgres instance and storage bucket in GCP. Used a paasword file on The VM to store Hostname, Username, and passwords. Used crontab to automate the bash script I created on the VM.

Backups up tables on-prem ------ transfer file from on prem to GCO storage bucket ------ connects to Cloud SQL database, truncates tables ------ import data from stored file in bucket. Works so well.

--
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/878c2702-6ad9-4507-9b2f-ddd823fa608e%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cannot delete created role (Postgres 11)

Oh, I could be happy to have the superuser privileges once you only give it to me!

Following to https://cloud.google.com/sql/docs/postgres/users 

Because Cloud SQL for PostgreSQL is a managed service, it restricts access to certain system procedures and tables that require advanced privileges. In Cloud SQL, customers cannot create or have access to users with superuser attributes.

That's why I cant revoke CONNECT privileges off the PUBLIC - because cloudsqlsuperuser owns it as well as observer somehow got it from cloudsqlsuperuser - I can't explain! And I have no access to cloudsqlsuperuser account, because:

The postgres user is part of the cloudsqlsuperuser role, and has the following attributes (privileges): CREATEROLE, CREATEDB, and LOGIN. It does not have the SUPERUSER or REPLICATION attributes.

On Tuesday, April 21, 2020 at 11:50:12 PM UTC+3, David (Google Cloud Support) wrote:

Since the issue seems to be with the connect privilege, this StackOverflow post may be worth reading as it explains how to revoke the connect privilege. That specific privilege  seems to be given by default upon some object creation to PUBLIC, which may be why you are having difficulties removing it.

If you are having difficulties with the superuser, you should consider using that user, and keep in mind that you can always change its password in the GCP console.

If the recommendation made in StackOverflow does not help and you still believe that this is a bug, as well as further investigation, I suggest that you make a StackOverflow post yourself to perhaps get some support from other users, as well as create an Issue Tracker entry following instructions.

Polybius Tech OÜ is a limited liability company registered in Estonia. Registered number: 14420450. Registered office: Tartu mnt. 43, Tallinn 10128, Estonia.

Any information sent by e-mail by Polybius Tech OÜ ("Polybius") or any of its affiliates is confidential and intended solely for the use of the individual or entity to whom it is addressed. If you are not the named addressee you should not disseminate, distribute or copy this email. If you have received this message in error please delete it and any copies of it and notify the sender immediately. Note that the contents of an attachment to this e-mail may contain software viruses, which could damage your computer system. While Polybius has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening the attachment.

--
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/6cf61165-ddba-4055-8aba-8d385470539a%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cannot delete created role (Postgres 11)

Try these two then delete again.

REVOKE ALL PRIVILEGES ON DATABASE somebase from observer CASCADE;

REVOKE ALL PRIVILEGES ON SCHEMA public from observer CASCADE;

On Wednesday, April 8, 2020 at 10:11:21 PM UTC+10, Mikheev Aleksandr wrote:

I created user observer using postgres user on my PostgreSQL 11 instance and I don't need it anymore. But after all I can't delete it - pgAdmin showing me that my user have connect privileges granted by the cloudsqlsuperuser, and I cannot revoke it to delete my earlier created user account!

somebase=> REVOKE ALL PRIVILEGES ON DATABASE "somebase" FROM observer; 
REVOKE 
somebase=> DROP ROLE observer; 
ERROR: role "observer" cannot be dropped because some objects depend on it DETAIL: privileges for database somebase

I also tried to delete it using gcloud cli and CloudSQL console both and failed. So how to delete it now?

Polybius Tech OÜ is a limited liability company registered in Estonia. Registered number: 14420450. Registered office: Tartu mnt. 43, Tallinn 10128, Estonia.

Any information sent by e-mail by Polybius Tech OÜ ("Polybius") or any of its affiliates is confidential and intended solely for the use of the individual or entity to whom it is addressed. If you are not the named addressee you should not disseminate, distribute or copy this email. If you have received this message in error please delete it and any copies of it and notify the sender immediately. Note that the contents of an attachment to this e-mail may contain software viruses, which could damage your computer system. While Polybius has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening the attachment.

--
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/30e29bc8-b554-4582-a8cb-9d72d964eaca%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cannot delete created role (Postgres 11)

Since the issue seems to be with the connect privilege, this StackOverflow post may be worth reading as it explains how to revoke the connect privilege. That specific privilege  seems to be given by default upon some object creation to PUBLIC, which may be why you are having difficulties removing it.

If you are having difficulties with the superuser, you should consider using that user, and keep in mind that you can always change its password in the GCP console.

If the recommendation made in StackOverflow does not help and you still believe that this is a bug, as well as further investigation, I suggest that you make a StackOverflow post yourself to perhaps get some support from other users, as well as create an Issue Tracker entry following instructions.

--
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/5744c685-bce1-4e7a-b9d0-72eb43e29a08%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cannot delete created role (Postgres 11)

Hi! No, it doesn't! Because 'observer' owns no objects, but 'connect' PRIVILEGE!

ERROR:  role "observer" cannot be dropped because some objects depend on it

DETAIL:  privileges for database somebase

I consider it's as a bug, because observer's 'connect' privilege was set by 'cloudsqlsuperuser', and I cannot remove it, because I have no superuser rights, as I have no access to the cloudsqlsuperuser account as well!

On Wednesday, April 8, 2020 at 10:27:21 PM UTC+3, Katayoon (Cloud Platform Support) wrote:

Hi,

As the error message clearly denotes, the reason you cannot delete the user is because that user has objects that depend on it. You first need to drop those objects or reassign them to other user. This thread on Stack Exchange discuss how to find the objects owned by the user. As explained in this Stack Overflow thread, you may try to revoke all the possible privileges with multiple statements like:

REASSIGN OWNED BY observer TO postgres;  -- or TO user

DROP OWNED BY observer;

REVOKE ALL PRIVILEGES ON ALL TABLES IN SCHEMA public FROM observer;

REVOKE ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA public FROM observer;

REVOKE ALL PRIVILEGES ON ALL FUNCTIONS IN SCHEMA public FROM observer;

DROP USER observer;

In order to be able to run those commands, you will need to connect to the instance first. Hope this resolves the issue? 

Polybius Tech OÜ is a limited liability company registered in Estonia. Registered number: 14420450. Registered office: Tartu mnt. 43, Tallinn 10128, Estonia.

Any information sent by e-mail by Polybius Tech OÜ ("Polybius") or any of its affiliates is confidential and intended solely for the use of the individual or entity to whom it is addressed. If you are not the named addressee you should not disseminate, distribute or copy this email. If you have received this message in error please delete it and any copies of it and notify the sender immediately. Note that the contents of an attachment to this e-mail may contain software viruses, which could damage your computer system. While Polybius has taken every reasonable precaution to minimise this risk, we cannot accept liability for any damage which you sustain as a result of software viruses. You should carry out your own virus checks before opening the attachment.

--
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/212d5a38-87ee-4b65-8a19-31bae8053669%40googlegroups.com.

Re: [google-cloud-sql-discuss] CPU core downgrade

Thanks, we did the upgrade and it took about 5 mins. Our workloads were taking ~30% CPU, on average. I don't think we're database-bound though, but it's prob a good idea to upgrade.

On Wednesday, April 15, 2020 at 6:13:57 PM UTC-3, Derek Maxwell wrote:

I've resized Google Cloud SQL instances numerous times, both up and down. Downtime is typically less than 5 mins.

Just curious - what kinds of workloads are you running? Is your single core machine keeping up? Keep in mind that Google's "cores" are more like the "threads" on your local PC, so I've found that anything less than a dual core is almost unusable for production work. 

Derek Maxwell

On Wed, Apr 15, 2020 at 11:46 AM Mark Nordine <mark....@gmail.com> wrote:

I had a couple of questions I couldn't find in the documentation.

1. If I upgrade my instance, say, from a single core to a quad-core machine, can I go back to single core instance?

2. If I do upgrade, is there downtime? If so, how much (our instance takes a few minutes for a restart)?

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/ebbb5315-ae20-4398-ad53-3e0010e9e790%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/b9e6cc4b-2906-456d-92bb-5c7223aa2c5a%40googlegroups.com.

Re: [google-cloud-sql-discuss] CPU core downgrade

I've resized Google Cloud SQL instances numerous times, both up and down. Downtime is typically less than 5 mins.

Just curious - what kinds of workloads are you running? Is your single core machine keeping up? Keep in mind that Google's "cores" are more like the "threads" on your local PC, so I've found that anything less than a dual core is almost unusable for production work. 

Derek Maxwell

On Wed, Apr 15, 2020 at 11:46 AM Mark Nordine <mark.nordine@gmail.com> wrote:

I had a couple of questions I couldn't find in the documentation.

1. If I upgrade my instance, say, from a single core to a quad-core machine, can I go back to single core instance?

2. If I do upgrade, is there downtime? If so, how much (our instance takes a few minutes for a restart)?

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/ebbb5315-ae20-4398-ad53-3e0010e9e790%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/CAHYX6i7WPe%3Duigw_n%3D_F4%3DHWUBB9Ym8BOuqF1tJmHp7DjF_enA%40mail.gmail.com.

[google-cloud-sql-discuss] CPU core downgrade

I had a couple of questions I couldn't find in the documentation.

1. If I upgrade my instance, say, from a single core to a quad-core machine, can I go back to single core instance?

2. If I do upgrade, is there downtime? If so, how much (our instance takes a few minutes for a restart)?

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/ebbb5315-ae20-4398-ad53-3e0010e9e790%40googlegroups.com.

[google-cloud-sql-discuss] Re: Sql Logs filled with Logon Login failed for user 'a-...-\a-...-$'.

Thanks for your clear and prompt response. That helps assuage my concerns that I had broken something.

Travis

On Tuesday, April 14, 2020 at 7:30:53 AM UTC-6, Katayoon (Cloud Platform Support) wrote:

Hi Travis,

This error can be ignored for the moment until the Cloud SQL product team roll out a fix from Microsoft, for which there is currently no timeline. Microsoft seems have released an update in which the Customer Experience Improvement Program (CEIP) has been removed from the product (additional more info link). The workaround to make the issue disappear is to grant CONNECT permission on your Cloud SQL Endpoint (localhost) endpoint to public which I wouldn't recommend for a production instance. Disabling CEIP only disables the upload to Microsoft and not the collection of data which is what results in the error.

--
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/d6f8e32a-6b53-453a-ac22-95f84703c620%40googlegroups.com.

[google-cloud-sql-discuss] Re: When will the max_connections setting exit beta?

Hi Mohamed,

There is no ETA as to when it will be production ready since this has to be approved by the Cloud SQL product team. Any updates or release will be available on Cloud SQL Release notes 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/fe7854a5-722c-49cf-ab91-bd9a72bf954b%40googlegroups.com.

[google-cloud-sql-discuss] Re: Sql Logs filled with Logon Login failed for user 'a-...-\a-...-$'.

Hi Travis,

This error can be ignored for the moment until the Cloud SQL product team roll out a fix from Microsoft, for which there is currently no timeline. Microsoft seems have released an update in which the Customer Experience Improvement Program (CEIP) has been removed from the product (additional more info link). The workaround to make the issue disappear is to grant CONNECT permission on your Cloud SQL Endpoint (localhost) endpoint to public which I wouldn't recommend for a production instance. Disabling CEIP only disables the upload to Microsoft and not the collection of data which is what results in the error.

--
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/755e8f6f-0bca-4942-a6a2-099cd22831bf%40googlegroups.com.

[google-cloud-sql-discuss] Sql Logs filled with Logon Login failed for user 'a-...-\a-...-$'.

My Sql Server logs (Cloud Sql, of course) are full with the following:

Logon Login failed for user 'a-xxxxxxxxxxxx-\a-xxxxxxxxxxxx-$'. Reason: Token-based server access validation failed with an infrastructure error. Login lacks connect endpoint permission

(I redacted the account, just in case its sensitive).

These are coming through about every 20 minutes 24/7, I have no idea what that account is. 

My best guess it its some sort of service to check on the server periodically, but no clue. My app engine app and sql proxy connections are working just fine.

Any ideas?

Thanks

Travis

--
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/37712b02-a5a3-4222-b7f2-896fe26127fa%40googlegroups.com.

[google-cloud-sql-discuss] Re: Postgres 12 - Missing column s.consrc

Hi Katayoon, 

Thank you for your answer. I had an old 2.2 version, which is why it wasn't working! I upgraded GDAL to 3.0.4 and it's all good now!

Thank you again for your help

Best,

Hugo

This email and any attachments contains privileged and confidential information intended only for the use of the addressee(s). If you are not an intended recipient of this email, you are hereby notified that any dissemination, copying or use of information is strictly prohibited. If you received this email in error or without authorization, please delete the email from your system and notify us immediately by sending us an email. If you need any further assistance, please send a message to hello@artefact.com.

This email and any attachments contains privileged and confidential information intended only for the use of the addressee(s). If you are not an intended recipient of this email, you are hereby notified that any dissemination, copying or use of information is strictly prohibited. If you received this email in error or without authorization, please delete the email from your system and notify us immediately by sending us an email. If you need any further assistance, please send a message to hello@artefact.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/98350227-d749-425d-ae6a-9f85a3ffce49%40googlegroups.com.

[google-cloud-sql-discuss] When will the max_connections setting exit beta?

Hi, is there any eta for when the max_connections setting for Google Cloud SQL MySQL instances will exit beta and be fully supported? I see it's been in beta for over a year, is it production ready right now?

Unfortunately this is the limiting factor keeping me from moving to GCP

--
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/509c6017-d7ac-4466-8c1e-1e023c85e65d%40googlegroups.com.

[google-cloud-sql-discuss] Re: CSV export with replication

Rafael, 

Quite rightly, setting the flag by using the Alter SQL command requires the SUPER USER access, which is not available with the CloudSQL[1]. The flag, hot_standby_feedback however should work as a viable alternative. 

I am glad to know that you were able resolve the permission issue. 

[1]https://cloud.google.com/sql/docs/postgres/users#superuser_restrictions

--
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/d3a87f6f-52a2-4c8e-b99b-060392c1dda3%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Cloud SQL Database Broken

I was back up after about 2.5 hours
Just glad no data was lost

On Thu, 9 Apr 2020 at 19:25, 'Aref Amiri (Cloud Platform Support)' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com> wrote:

Hi Jan,

There was a reported wide spread incident that has affected multiple Google Cloud Platform Services, including Cloud SQL. The incident is marked as resolved and your instance should up and running, however, if you still experience any issue, it is best to create a Private Issue Tracker, and provide additional information for further investigation.

--
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/8c1b7876-56f2-4f00-a6d4-388accb280d3%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/CAKkrQ9stHpe-1voTYbA6XLiW1QfjS1zht4jrGjM77KpE05LA8A%40mail.gmail.com.

[google-cloud-sql-discuss] Re: CSV export with replication

Hi Olu:

My comment below.

Thanks 

El jueves, 9 de abril de 2020, 15:36:57 (UTC+2), Olu escribió:

Hello, Rafael

There are a number of reasons why the error may have been returned. In fact, a similar issue reported in the past was traced to the amount of workloads on the CloudSQL instance at the time. Also, the issue sometimes was found to be transient as there were times observed in the past that restarting the Instance resolves the issue. For better troubleshooting of the issue, which may involve reviewing configurations on your Project, I recommend you contact the GCP Support Engineers[1] or if you think this issue is a bug and you are using the appropriate User account but it is failing, then open an issue using this link[2]. 

I already fixed the error were the permissions. But I'll check the links and take note for future problems 

About the flag, hot_standby_feedback, from the information provided on this CloudSQL for Postgres page[3], the flag is actually supported. I did a test on my test environment and I was able to successfully add the flag without any additional access or permission. If you can't change the flag, can you provide information about your experience? Do you have an error reported or the field is grayed out? 

 i thing was an alter table "ALTER SYSTEM SET hot_standby_feedback TO on"  maybe need to execute the command.

This information will be helpful to understand what may be the cause of your inability to change the flag and possibly, the same reason may be responsible for the failing export using your user account.  

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

[2]https://developers.google.com/issue-tracker/#public_users

[3]https://cloud.google.com/sql/docs/postgres/flags#postgres-h

--
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/a20eaf52-cf8f-4106-a231-c41ce00474bc%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL Database Broken

Hi Jan,

There was a reported wide spread incident that has affected multiple Google Cloud Platform Services, including Cloud SQL. The incident is marked as resolved and your instance should up and running, however, if you still experience any issue, it is best to create a Private Issue Tracker, and provide additional information for further investigation.

--
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/8c1b7876-56f2-4f00-a6d4-388accb280d3%40googlegroups.com.

[google-cloud-sql-discuss] Re: Postgres 12 - Missing column s.consrc

Hi Hugo,

We need more clarification on your codebase and the steps you are taking which ends up with this error to be able to dig into the issue. Could you let us know if you are using any dependency or third-party tools in your codebase? 

I am asking this because on a Stack Exchange thread, this error occurred due to a bug on GDAL PG12 and an upgrade to GDAL has fixed 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/e8edabed-fbfa-49d6-aa45-c0b308b186b6%40googlegroups.com.

[google-cloud-sql-discuss] Re: CSV export with replication

Hello, Rafael

There are a number of reasons why the error may have been returned. In fact, a similar issue reported in the past was traced to the amount of workloads on the CloudSQL instance at the time. Also, the issue sometimes was found to be transient as there were times observed in the past that restarting the Instance resolves the issue. For better troubleshooting of the issue, which may involve reviewing configurations on your Project, I recommend you contact the GCP Support Engineers[1] or if you think this issue is a bug and you are using the appropriate User account but it is failing, then open an issue using this link[2]. 

About the flag, hot_standby_feedback, from the information provided on this CloudSQL for Postgres page[3], the flag is actually supported. I did a test on my test environment and I was able to successfully add the flag without any additional access or permission. If you can't change the flag, can you provide information about your experience? Do you have an error reported or the field is grayed out? 

This information will be helpful to understand what may be the cause of your inability to change the flag and possibly, the same reason may be responsible for the failing export using your user account.  

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

[2]https://developers.google.com/issue-tracker/#public_users

[3]https://cloud.google.com/sql/docs/postgres/flags#postgres-h

--
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/88ef4458-7f47-48fd-b1bf-0b2b61095c1b%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL creation failed during migration

Hi Simon,

We experienced an issue with Google Cloud infrastructure components which impacted multiple services including Cloud SQL HA instances, yesterday. It seems you were affected by that incident. The issue is resolved now but if you are still experiencing any issue with your Cloud SQL instance, I recommend to raise a ticket with support via your support package (if you have the support package) or create a ticket in the GCP Issue Tracker so that we will investigate it there efficiently. 

--
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/e1f16a7d-11fe-4b6b-ac70-65e8510429ed%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cannot delete created role (Postgres 11)

Hi,

As the error message clearly denotes, the reason you cannot delete the user is because that user has objects that depend on it. You first need to drop those objects or reassign them to other user. This thread on Stack Exchange discuss how to find the objects owned by the user. As explained in this Stack Overflow thread, you may try to revoke all the possible privileges with multiple statements like:

REASSIGN OWNED BY observer TO postgres;  -- or TO user

DROP OWNED BY observer;

REVOKE ALL PRIVILEGES ON ALL TABLES IN SCHEMA public FROM observer;

REVOKE ALL PRIVILEGES ON ALL SEQUENCES IN SCHEMA public FROM observer;

REVOKE ALL PRIVILEGES ON ALL FUNCTIONS IN SCHEMA public FROM observer;

DROP USER observer;

In order to be able to run those commands, you will need to connect to the instance first. Hope this resolves 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/8731eaaa-2f23-436d-b9e8-17e9fc041110%40googlegroups.com.

[google-cloud-sql-discuss] Re: Metrics missing in Postgres version 12

I'm able to see this issue as well. I have reported it to the Cloud SQL engineering team. Please follow this Issue Tracker for any updates.

Please note that PostgreSQL 12 in Cloud SQL is still in beta and not recommended to be used in production just yet.

--
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/6d054eb6-ba14-45c8-80d5-ae2c5c70fc72%40googlegroups.com.

[google-cloud-sql-discuss] Postgres 12 - Missing column s.consrc

Hi, 

While trying to run my codebase on New GCP Cloud SQL postgres 12 release, I got the following error message: 

ERROR 1: ERROR:  column s.consrc does not exist

LINE 1: ...nrelid = c.oid AND a.attnum = ANY (s.conkey) AND (s.consrc L...

                                                             ^

HINT:  Perhaps you meant to reference the column "s.conkey" or the column "s.conbin".

ERROR 1: ERROR:  column s.consrc does not exist

LINE 1: ...nrelid = c.oid AND a.attnum = ANY (s.conkey) AND (s.consrc L...

                                                             ^

HINT:  Perhaps you meant to reference the column "s.conkey" or the column "s.conbin".

Any help is welcome :) 

Thanks

Hugo

This email and any attachments contains privileged and confidential information intended only for the use of the addressee(s). If you are not an intended recipient of this email, you are hereby notified that any dissemination, copying or use of information is strictly prohibited. If you received this email in error or without authorization, please delete the email from your system and notify us immediately by sending us an email. If you need any further assistance, please send a message to hello@artefact.com.

This email and any attachments contains privileged and confidential information intended only for the use of the addressee(s). If you are not an intended recipient of this email, you are hereby notified that any dissemination, copying or use of information is strictly prohibited. If you received this email in error or without authorization, please delete the email from your system and notify us immediately by sending us an email. If you need any further assistance, please send a message to hello@artefact.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/8aa29f47-14be-4d86-9b3b-d87c3257fbd2%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL creation failed during migration

Just in case anyone else had this issue, it seems you either raise a ticket with support or stick it out and hope they find your instance was impacted.

On Wednesday, April 8, 2020 at 6:33:56 PM UTC+1, Simon Smethurst-McIntyre wrote:

Hi

During the literally just happened Google Cloud instance our Cloud SQL instance tried to fail over to its replica and it all seems to have gone very wrong. There's now a red exclamation mark next to the instance name in the cloud console and when you go to details it says failed to create. The mysql log shows the instance shutting down.

All my options to start the instance or do anything except delete it are greyed out.

Does anyone know how I can get this instance back up 

--
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/b316a4e1-de10-4cc0-b1c0-a846e75a4dab%40googlegroups.com.

[google-cloud-sql-discuss] Cloud SQL creation failed during migration

Hi

During the literally just happened Google Cloud instance our Cloud SQL instance tried to fail over to its replica and it all seems to have gone very wrong. There's now a red exclamation mark next to the instance name in the cloud console and when you go to details it says failed to create. The mysql log shows the instance shutting down.

All my options to start the instance or do anything except delete it are greyed out.

Does anyone know how I can get this instance back up 

--
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/10ab52c2-4479-4891-96e2-828a55a9d9f0%40googlegroups.com.

[google-cloud-sql-discuss] Cloud SQL Database Broken

Hi there,

Oor cloud SQL instance just went dead for project id lula-build and sql instance lula-build-sql-prod  

We didn't make any changes to the instance, it's been running fine for probably over a year.

Last backup was 3am this morning, so restoring from a backup would mean losing a whole day of data.

Is there someone that can assist?

Kind regards

Jan

--
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/01fcf1e4-12af-4eae-92b0-fc8c7b8620eb%40googlegroups.com.

[google-cloud-sql-discuss] Re: CSV export with replication

Hi, 

Thanks for your reply, I saw the official documentation and I can't change this flag link [1]. I tried another approach with "gcloud sql export csv" but I have other error

ERROR: (gcloud.sql.export.csv) [ERROR_RDBMS] system error occurred pre-export

Thanks 

[1] https://cloud.google.com/sql/docs/postgres/flags#list-flags-postgres
El miércoles, 8 de abril de 2020, 6:38:39 (UTC+2), yananc escribió:

Hi, 

Configuring database flags requires corresponding roles / permissions. I suggest you contact the Cloud SQL Administrator of the instance to apply for the privilege in order to complete the operation. 

Hope it helps!

On Tuesday, April 7, 2020 at 1:05:45 PM UTC-4, rafael valenzuela moraleda wrote:

Hi all,

I've this error when try to export tables to csv :

• ERROR:  canceling statement due to conflict with recovery
• DETAIL:  User query might have needed to see row versions that must be removed

Normally fix it when active this flag hot_standby_feedback  but I cant't because I shoolbe no a super user  , any idea?

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/ae01fae8-fe3f-4498-8540-5d1a2684db39%40googlegroups.com.