July 2020

Friday, July 31, 2020

[google-cloud-sql-discuss] Re: I want to know which queries are getting executed in google cloud sql. how do i do that

Cloud SQL is a managed environment, and provides logging information without you having to enjoy super permissions to access it. Related details are to be found on the "Cloud SQL logging" documentation page.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/14bacd42-ac9b-44d6-9570-4e4bdc7f1233o%40googlegroups.com.

[google-cloud-sql-discuss] Re: Using On-prem NTP time service for CloudSQL(PostgreSQL)

Thank you for providing clarification to your needs. I think I understand this request as trying to keep local clocks in sync to match the time used by Google CloudSQL. Please let me know if my understanding is wrong.

As you may already know, all Google Cloud Applications and APIs use the same NTP server time source including Cloud Functions, Cloud SQL, Datastore, BigTable, BigQuery, and DataFlow.

So, if indeed your target is to ensure that your Local Clocks are in sync with the same NTP Server, I believe you can find instructions about the required configurations here[1].

For more information about the Google Public NTP Servers, I found these articles[2][3] interesting and I think they may be helpful to guide your thoughts.

[1]https://developers.google.com/time/guides

[2]https://cloudblog.withgoogle.com/products/gcp/making-every-leap-second-count-with-our-new-public-ntp-servers/amp/

[3]https://developers.google.com/time/

--
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/420a8278-ed9f-4f0c-bb00-cf4c43580139o%40googlegroups.com.

[google-cloud-sql-discuss] I want to know which queries are getting executed in google cloud sql. how do i do that

Since we dont have super permission in google cloud database, how to obtain query log for cloud sql database.

--
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/10d26af0-9954-4b8c-b4ff-d506adf981fco%40googlegroups.com.

Thursday, July 30, 2020

[google-cloud-sql-discuss] Re: Exception while connecting to mysql over private IP

Based on what you are suggesting, you are having issues with your code and not Cloud SQL itself as that works. I highly suggest that you consider using the Cloud SQL proxy over a simple Private IP as it provides secure access to your instances without the need for Authorized networks or for configuring SSL.

This issue isn't best suited for Google Groups. Although this is a valid issue, I suggest that you post it in the Public Issue Tracker where you can provide a reproducible sample which can be further analyzed as this Stack trace does provide much information. This is viable if you believe that this is an issue with the product. Alternativy, you can post this on Stack Overflow where members of the community can help you with your Spring Application. Google Groups is best suited for Product discussions, releases, service announcements and such. More details on our Community Support can be found here.

--
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/2eaa1d0e-42b5-4572-9e19-065d68844e97o%40googlegroups.com.

[google-cloud-sql-discuss] Exception while connecting to mysql over private IP

Hi,

I am getting the following error while connecting to the MySql instance.

The connection to the database is over a private IP.

The same setup is working on a normal co-located server.

I am able to use the mysql client to connect to the database over the private IP.

The application being deployed is a Spring based application.

2020-07-30 09:31:03,369 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (JCA PoolFiller) IJ000610: Unable to fill pool: java:jboss/datasources/ACADEMY: javax.resource.ResourceException: IJ031084: Unable to create connection

at org.jboss.ironjacamar.jdbcadapters@1.4.22.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:345)

at org.jboss.ironjacamar.jdbcadapters@1.4.22.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:352)

at org.jboss.ironjacamar.jdbcadapters@1.4.22.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:287)

at org.jboss.ironjacamar.impl@1.4.22.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.createConnectionEventListener(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1322)

at org.jboss.ironjacamar.impl@1.4.22.Final//org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.fillTo(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:1142)

at org.jboss.ironjacamar.impl@1.4.22.Final//org.jboss.jca.core.connectionmanager.pool.mcp.PoolFiller.run(PoolFiller.java:97)

at java.base/java.lang.Thread.run(Thread.java:844)

Caused by: com.mysql.cj.jdbc.exceptions.CommunicationsException: Communications link failure

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

at com.mysql@8.0.20//com.mysql.cj.jdbc.exceptions.SQLError.createCommunicationsException(SQLError.java:174)

at com.mysql@8.0.20//com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:64)

at com.mysql@8.0.20//com.mysql.cj.jdbc.ConnectionImpl.createNewIO(ConnectionImpl.java:836)

at com.mysql@8.0.20//com.mysql.cj.jdbc.ConnectionImpl.<init>(ConnectionImpl.java:456)

at com.mysql@8.0.20//com.mysql.cj.jdbc.ConnectionImpl.getInstance(ConnectionImpl.java:246)

at com.mysql@8.0.20//com.mysql.cj.jdbc.NonRegisteringDriver.connect(NonRegisteringDriver.java:197)

at org.jboss.ironjacamar.jdbcadapters@1.4.22.Final//org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:321)

... 6 more

Caused by: com.mysql.cj.exceptions.CJCommunicationsException: Communications link failure

--
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/12e8f1f3-852b-4c87-9f66-8a475f2a81c2o%40googlegroups.com.

Wednesday, July 29, 2020

Re: [google-cloud-sql-discuss] Re: Cloud SQL Dump time

Hi Rajat,

Thank you for providing us all the information. It definitely looks like you are getting consistent results of the same problem.

I tried to reproduce the issue and didn't have any problems, but it's hard to tell since I don't have 2GB of data to put into the database to test and your environment could be very different. I also searched for other related known issues and didn't find any. I'm suspecting this could be an isolated incident as it would have been reported by now. The only thing we haven't eliminated yet from your setup is the connection.

Would you please try from another connection? If that doesn't work on another connection, you will probably have to open an issue privately in Google's Issue Tracker[1] or open a support ticket[2] as it's an isolated case. But before you do that, please test another connection. This would avoid you waiting longer for our engineers to try and find an issue which maybe doesn't exist on our side. It would save you time.

Please eliminate the connection possibility and let us know. Thanks in advance.

[1] https://developers.google.com/issue-tracker

[2] https://cloud.google.com/support#tab2

--
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/8fbe641d-93d1-42a5-8682-17433c1b38e1o%40googlegroups.com.

[google-cloud-sql-discuss] Re: Using On-prem NTP time service for CloudSQL(PostgreSQL)

Hi David,

Thanks for sharing the details.

My requirements is to sync with my on-premise time server. Not with Cloud SQL on-prem.

Is this possible?

Thanks

Suhas

On Monday, July 27, 2020 at 7:48:52 PM UTC+5:30, David (Google Cloud Support) wrote:

I could not find any documentation indicating that syncing a Cloud instance with an on-prem PostgreSQL was possible, only migrating from on-prem to Cloud.
However, you can change the timezone of your Cloud instance from the default value. You can do so by editing your existing instance's `default_time_zone` flag through the console or through running a gcloud command. This information might prove useful to 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/a2d5946f-5cbb-4936-877a-100ef0b0cfa2o%40googlegroups.com.

Tuesday, July 28, 2020

[google-cloud-sql-discuss] Re: Point-in-time recovery storage overhead?

Hello Andrew,

This is due to when enabling PITR it is necessary to archive the Write Ahead Logs (WAL)[1]. The archiving is performed automatically, which by default is every 5 minutes regardless of activity on the database.

Similar to binlogging in MySQL, we will only keep the last 7 days of archived WAL logs at any given time.

[1] https://cloud.google.com/sql/docs/postgres/backup-recovery/pitr#disk-usage

On Thursday, July 23, 2020 at 8:55:03 AM UTC-4, Andrew Smith wrote:

Hello!

We have set up a recent Cloud SQL instance running PostgreSQL 12 and point-in-time recovery turned on. We picked the smallest instance size and gave it 10GiB of storage. This instance has sat virtually idle with maybe less than 1k reads/writes over the past 10 days.

Today, I noticed in the console that the instance is currently using over 31GiB of storage. It has ticked up at a rate of several GiB/day and appears to be bouncing off of a ceiling of 32GiB currently.

When I log in with psql, the sum of the sizes of tables for our database is less than 1MiB total:

agency=> \d+
List of relations
Schema | Name | Type | Owner | Size | Description
--------+-------------------+-------+-------+------------+-------------
public | ***************** | table | ***** | 8192 bytes |
public | ***************** | table | ***** | 8192 bytes |
public | ***************** | table | ***** | 16 kB |
public | ***************** | table | ***** | 8192 bytes |
public | ***************** | table | ***** | 8192 bytes |
public | ***************** | table | ***** | 8192 bytes |
public | ***************** | table | ***** | 16 kB |
(7 rows)

PostgreSQL's own internal metadata is light too:

postgres=> \dS+
List of relations
Schema | Name | Type | Owner | Size | Description
------------+---------------------------------+-------+---------------+------------+-------------
pg_catalog | pg_aggregate | table | cloudsqladmin | 56 kB |
pg_catalog | pg_am | table | cloudsqladmin | 40 kB |
pg_catalog | pg_amop | table | cloudsqladmin | 80 kB |
pg_catalog | pg_amproc | table | cloudsqladmin | 56 kB |
pg_catalog | pg_attrdef | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_attribute | table | cloudsqladmin | 464 kB |
pg_catalog | pg_auth_members | table | cloudsqladmin | 40 kB |
pg_catalog | pg_authid | table | cloudsqladmin | 48 kB |
pg_catalog | pg_available_extension_versions | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_available_extensions | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_cast | table | cloudsqladmin | 48 kB |
pg_catalog | pg_class | table | cloudsqladmin | 136 kB |
pg_catalog | pg_collation | table | cloudsqladmin | 384 kB |
pg_catalog | pg_config | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_constraint | table | cloudsqladmin | 48 kB |
pg_catalog | pg_conversion | table | cloudsqladmin | 56 kB |
pg_catalog | pg_cursors | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_database | table | cloudsqladmin | 48 kB |
pg_catalog | pg_db_role_setting | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_default_acl | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_depend | table | cloudsqladmin | 480 kB |
pg_catalog | pg_description | table | cloudsqladmin | 368 kB |
pg_catalog | pg_enum | table | cloudsqladmin | 0 bytes |
pg_catalog | pg_event_trigger | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_extension | table | cloudsqladmin | 48 kB |
pg_catalog | pg_file_settings | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_foreign_data_wrapper | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_foreign_server | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_foreign_table | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_group | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_hba_file_rules | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_index | table | cloudsqladmin | 64 kB |
pg_catalog | pg_indexes | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_inherits | table | cloudsqladmin | 0 bytes |
pg_catalog | pg_init_privs | table | cloudsqladmin | 56 kB |
pg_catalog | pg_language | table | cloudsqladmin | 48 kB |
pg_catalog | pg_largeobject | table | cloudsqladmin | 0 bytes |
pg_catalog | pg_largeobject_metadata | table | cloudsqladmin | 0 bytes |
pg_catalog | pg_locks | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_matviews | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_namespace | table | cloudsqladmin | 48 kB |
pg_catalog | pg_opclass | table | cloudsqladmin | 48 kB |
pg_catalog | pg_operator | table | cloudsqladmin | 144 kB |
pg_catalog | pg_opfamily | table | cloudsqladmin | 48 kB |
pg_catalog | pg_partitioned_table | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_pltemplate | table | cloudsqladmin | 48 kB |
pg_catalog | pg_policies | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_policy | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_prepared_statements | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_prepared_xacts | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_proc | table | cloudsqladmin | 672 kB |
pg_catalog | pg_publication | table | cloudsqladmin | 0 bytes |
pg_catalog | pg_publication_rel | table | cloudsqladmin | 0 bytes |
pg_catalog | pg_publication_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_range | table | cloudsqladmin | 40 kB |
pg_catalog | pg_replication_origin | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_replication_origin_status | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_replication_slots | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_rewrite | table | cloudsqladmin | 632 kB |
pg_catalog | pg_roles | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_rules | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_seclabel | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_seclabels | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_sequence | table | cloudsqladmin | 0 bytes |
pg_catalog | pg_sequences | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_settings | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_shadow | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_shdepend | table | cloudsqladmin | 40 kB |
pg_catalog | pg_shdescription | table | cloudsqladmin | 48 kB |
pg_catalog | pg_shseclabel | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_stat_activity | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_all_indexes | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_all_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_archiver | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_bgwriter | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_database | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_database_conflicts | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_gssapi | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_progress_cluster | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_progress_create_index | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_progress_vacuum | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_replication | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_ssl | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_subscription | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_sys_indexes | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_sys_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_user_functions | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_user_indexes | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_user_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_wal_receiver | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_xact_all_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_xact_sys_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_xact_user_functions | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stat_xact_user_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_statio_all_indexes | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_statio_all_sequences | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_statio_all_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_statio_sys_indexes | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_statio_sys_sequences | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_statio_sys_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_statio_user_indexes | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_statio_user_sequences | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_statio_user_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_statistic | table | cloudsqladmin | 256 kB |
pg_catalog | pg_statistic_ext | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_statistic_ext_data | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_stats | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_stats_ext | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_subscription | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_subscription_rel | table | cloudsqladmin | 0 bytes |
pg_catalog | pg_tables | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_tablespace | table | cloudsqladmin | 48 kB |
pg_catalog | pg_timezone_abbrevs | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_timezone_names | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_transform | table | cloudsqladmin | 0 bytes |
pg_catalog | pg_trigger | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_ts_config | table | cloudsqladmin | 40 kB |
pg_catalog | pg_ts_config_map | table | cloudsqladmin | 56 kB |
pg_catalog | pg_ts_dict | table | cloudsqladmin | 48 kB |
pg_catalog | pg_ts_parser | table | cloudsqladmin | 40 kB |
pg_catalog | pg_ts_template | table | cloudsqladmin | 40 kB |
pg_catalog | pg_type | table | cloudsqladmin | 120 kB |
pg_catalog | pg_user | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_user_mapping | table | cloudsqladmin | 8192 bytes |
pg_catalog | pg_user_mappings | view | cloudsqladmin | 0 bytes |
pg_catalog | pg_views | view | cloudsqladmin | 0 bytes |
(126 rows)

So where is this storage growth coming from? It isn't like we are doing big inserts and deletes either. Is this some undeclared overhead of using point-in-time recovery? We haven't noticed this with other Cloud SQL instances. Any insights would be appreciated. Nothing on the point-in-time recovery documentation page or FAQ talked about this.

Thanks!

Andrew

--
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/53800d94-1df8-4948-a68f-383fc78bfb86o%40googlegroups.com.

Re: [google-cloud-sql-discuss] Re: Cloud SQL Dump time

Hi,

1) using a lunix machine

2) had a postgresql client

3) Done

4) this is a 160MB file for a schema backup in t format

this is a 480kB file for a schema backup in t format

this is a 200kB file for a schema backup in sql format

this is a 145Kb file for a schema backup in sql format

Also the Network stats:

Best,

Rajat

On Tuesday, 28 July, 2020 at 4:12:30 am UTC+5:30 Elliott (Google Cloud Platform Support) wrote:

Hello,

To make sure our steps match, you may follow the information here:

1) Find a Linux workstation (gLinux desktop is fine; remote SSH is fine as well if you want the backup somewhere else)

2) If you don't already have the Postgres CLI tools, you can install them: sudo apt-get install postgresql-client

3) Prepare the CloudSQL instance to accept a connection from the machine you are using. You can follow this guide to find the easiest way to do this if you are not sure how to.

4) You can then prepare to do the dump. Enter a directory with lots of space (relative to the size of the database) and then prepare by running

pg_dump -h <IP> -U postgres -F t postgres > export.sql

5) You will be prompted for your Postgres password; enter it and then the export will begin to a file called export.sql

I have included these steps to give you an idea of the process and to try it yourself and see if they work.

I will wait for your response.

Confidentiality Notice:

This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain confidential information that is legally privileged. If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this transmission is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender. Please destroy the original transmission and its attachments without reading or saving in any manner.

--
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/8e359bc9-2d28-45af-b6ab-349918c091d5n%40googlegroups.com.

[google-cloud-sql-discuss] Re: SQL Server Instance has got Stuck

Hi Michael,

I recommend to create a PRIVATE issue tracker and provide us with your project id and the instance id so that we would be able to dig into the issue. You may also check if your project is linked to a billing account to rule out any possible issue from your billing account which may affect your Cloud SQL instance.

Note that, Google Cloud Platform groups are reserved for general questions about GCP-end products and for reporting an issue you should create a ticket via the Issue Tracker or create a case via your support package if you have any.

--
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/5441a76f-fcc6-4e72-9add-9b62ae284c8ao%40googlegroups.com.

Monday, July 27, 2020

Re: [google-cloud-sql-discuss] Re: Cloud SQL Dump time

Hello,

To make sure our steps match, you may follow the information here:

1) Find a Linux workstation (gLinux desktop is fine; remote SSH is fine as well if you want the backup somewhere else)

2) If you don't already have the Postgres CLI tools, you can install them: sudo apt-get install postgresql-client

3) Prepare the CloudSQL instance to accept a connection from the machine you are using. You can follow this guide to find the easiest way to do this if you are not sure how to.

4) You can then prepare to do the dump. Enter a directory with lots of space (relative to the size of the database) and then prepare by running

pg_dump -h <IP> -U postgres -F t postgres > export.sql

5) You will be prompted for your Postgres password; enter it and then the export will begin to a file called export.sql

I have included these steps to give you an idea of the process and to try it yourself and see if they work.

I will wait for your response.

--
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/06a44958-2be4-4f2b-ab67-7e2394fa98d5o%40googlegroups.com.

[google-cloud-sql-discuss] SQL Server Instance has got Stuck

Hello,

Our SQL Server instance on "Full Stack Data Solution" project with IP: 35.231.30.29 has got stuck while deleting a user.

We ain't able to restart, stop, the instance or acces via gcloud shell.

Please help.

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/70c22105-e847-4c26-865f-368c2a4a3109o%40googlegroups.com.

[google-cloud-sql-discuss] Re: Using On-prem NTP time service for CloudSQL(PostgreSQL)

I could not find any documentation indicating that syncing a Cloud instance with an on-prem PostgreSQL was possible, only migrating from on-prem to Cloud.

However, you can change the timezone of your Cloud instance from the default value. You can do so by editing your existing instance's `default_time_zone` flag through the console or through running a gcloud command. This information might prove useful to 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/039b08f3-6304-4a7d-982f-6987b95fd295o%40googlegroups.com.

[google-cloud-sql-discuss] Re: Changing the default timezone and using my data center NTP service

Hi Suhas,

It seems your question is a duplicate of this one you posted on this thread. So, I recommend to continiue with the duplicate thread.

--
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/ad1f8938-5314-4ffe-8868-e8ead222d4c4o%40googlegroups.com.

Friday, July 24, 2020

[google-cloud-sql-discuss] Using On-prem NTP time service for CloudSQL(PostgreSQL)

Hi Team,

I've some Cloud SQL instances(PostgeSQL managed database services), design principle is to use synchronize the time with one existing in On-premise data center. As this is a managed service,how do I sync this NTP service with CloudSQL?

Any pointers would be highly appreciated.

Thanks

Suhas

--
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/81cb5291-3fc2-4bf7-86c0-61e25d766a57o%40googlegroups.com.

Thursday, July 23, 2020

[google-cloud-sql-discuss] Changing the default timezone and using my data center NTP service

Hello all,

New to this group.

Working on a solution where I need to use the existing NTP services from my on-prem data center to synchronize clocks. But not sure how to change the time settings for ProgreSQL managed database service on Google Cloud Platform.

Please share any solutions you all have come across to resolve this.

Thanks

Suhas

--
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/73564f39-f24b-4097-9bcd-eced73478d0eo%40googlegroups.com.

Wednesday, July 22, 2020

Re: [google-cloud-sql-discuss] Re: Cloud SQL Dump time

Hi Alexis,

Answer to your questions:

- Which Cloud SDK / mysql command did you use?

Using postgres pg_dump utility

- Is it doing it on more than one computer?

Yes, I tried it on GCP VM, its much smooth there arround 5-7 seconds. And 2 minutes for 130MB data dump.

- Did it use to work before?

No, earlier I had same issue, so used the cloud sql backup utility. But here I needed just schema so had to use this.

- Have you tried another instance?
Yes, Same issue

- How big roughly is this instance?
This instance is occuping 2GB total space, with 7-8 databases

-------------Original message------------

I am experiencing an weird behaviour while taking a backup, its taking 5-7 minutes to get a schema dump of size 125kB from a GCP Cloud SQL DB to local machine.

Is there something that can be tuned here?

Dump process:

File Size:

Network:

Best,

Rajat

Best,

Rajat

From: 'Alexis (Google Cloud Support)' via Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com>
Sent: Thursday, July 23, 2020 04:39
To: Google Cloud SQL discuss <google-cloud-sql-discuss@googlegroups.com>
Subject: [google-cloud-sql-discuss] Re: Cloud SQL Dump time

Hello Rajat,

There could be a lot of possibilities but we will try to assist the best we can.

It appears that you tried to copy/paste information below but it's not visible to me. Without posting personal information, would you please indicate which command you used and also if it does it on another computer.

Questions:

- Which Cloud SDK / mysql command did you use?

- Is it doing it on more than one computer?

- Did it use to work before?

- Have you tried another instance?

- How big roughly is this instance?

I don't know how much data you have, but if it's because it's too small, then we can try to replicate the problem as soon as you provide us with more info.

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/b6a61e2f-de39-45d1-a277-72d42b9deb1bo%40googlegroups.com.

[google-cloud-sql-discuss] Re: Cloud SQL Dump time

Hello Rajat,

There could be a lot of possibilities but we will try to assist the best we can.

Questions:

- Which Cloud SDK / mysql command did you use?

- Is it doing it on more than one computer?

- Did it use to work before?

- Have you tried another instance?

- How big roughly is this instance?

I don't know how much data you have, but if it's because it's too small, then we can try to replicate the problem as soon as you provide us with more info.

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/b6a61e2f-de39-45d1-a277-72d42b9deb1bo%40googlegroups.com.

[google-cloud-sql-discuss] Point-in-time recovery storage overhead?

Hello!

We have set up a recent Cloud SQL instance running PostgreSQL 12 and point-in-time recovery turned on. We picked the smallest instance size and gave it 10GiB of storage. This instance has sat virtually idle with maybe less than 1k reads/writes over the past 10 days.

Today, I noticed in the console that the instance is currently using over 31GiB of storage. It has ticked up at a rate of several GiB/day and appears to be bouncing off of a ceiling of 32GiB currently.

When I log in with psql, the sum of the sizes of tables for our database is less than 1MiB total:

agency=> \d+

List of relations

--------+-------------------+-------+-------+------------+-------------

public | ***************** | table | ***** | 16 kB |

public | ***************** | table | ***** | 16 kB |

(7 rows)

PostgreSQL's own internal metadata is light too:

postgres=> \dS+

List of relations

------------+---------------------------------+-------+---------------+------------+-------------

(126 rows)

So where is this storage growth coming from? It isn't like we are doing big inserts and deletes either. Is this some undeclared overhead of using point-in-time recovery? We haven't noticed this with other Cloud SQL instances. Any insights would be appreciated. Nothing on the point-in-time recovery documentation page or FAQ talked about this.

Thanks!

Andrew

--
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/5a780bac-2243-4e02-bc03-c28fdeaaead3n%40googlegroups.com.

[google-cloud-sql-discuss] Cloud SQL Dump time

I am experiencing an weird behaviour while taking a backup, its taking 5-7 minutes to get a schema dump of size 125kB from a GCP Cloud SQL DB to local machine.

Is there something that can be tuned here?

Dump process:

File Size:

Network:

Best,

Rajat

Confidentiality Notice:

--
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/2803e4b4-8d8d-4b68-860b-6035a6347277n%40googlegroups.com.

Google Cloud SQL- Unofficial blog

Pages

Friday, July 31, 2020

[google-cloud-sql-discuss] Re: I want to know which queries are getting executed in google cloud sql. how do i do that

[google-cloud-sql-discuss] Re: Using On-prem NTP time service for CloudSQL(PostgreSQL)

[google-cloud-sql-discuss] I want to know which queries are getting executed in google cloud sql. how do i do that

Thursday, July 30, 2020

[google-cloud-sql-discuss] Re: Exception while connecting to mysql over private IP

[google-cloud-sql-discuss] Exception while connecting to mysql over private IP

Wednesday, July 29, 2020

Re: [google-cloud-sql-discuss] Re: Cloud SQL Dump time

[google-cloud-sql-discuss] Re: Using On-prem NTP time service for CloudSQL(PostgreSQL)

Tuesday, July 28, 2020

[google-cloud-sql-discuss] Re: Point-in-time recovery storage overhead?

Re: [google-cloud-sql-discuss] Re: Cloud SQL Dump time

[google-cloud-sql-discuss] Re: SQL Server Instance has got Stuck

Monday, July 27, 2020

Re: [google-cloud-sql-discuss] Re: Cloud SQL Dump time

[google-cloud-sql-discuss] SQL Server Instance has got Stuck

[google-cloud-sql-discuss] Re: Using On-prem NTP time service for CloudSQL(PostgreSQL)

[google-cloud-sql-discuss] Re: Changing the default timezone and using my data center NTP service

Friday, July 24, 2020

[google-cloud-sql-discuss] Using On-prem NTP time service for CloudSQL(PostgreSQL)

Thursday, July 23, 2020

[google-cloud-sql-discuss] Changing the default timezone and using my data center NTP service

Wednesday, July 22, 2020

Re: [google-cloud-sql-discuss] Re: Cloud SQL Dump time

[google-cloud-sql-discuss] Re: Cloud SQL Dump time

[google-cloud-sql-discuss] Point-in-time recovery storage overhead?

[google-cloud-sql-discuss] Cloud SQL Dump time