Hello James,
Our Cloud SQL product team has been made aware this issue is still being experienced. You can follow the public report here[1]. I recommend to star the issue to receive any updates and to upvote the issue by selecting +1.
Any updates will be provided via the public facing report.
[1] https://issuetracker.google.com/147251210
On Friday, August 7, 2020 at 11:46:34 AM UTC-4, James Richardson wrote:
Hi, this thread is a few years old, but this is the exact problem that I am also having. Basically, the "export" process in gcloud sql DOES NOT export multiple tables (as described in the OP).Does anybody else know the solution? Is it just a bug that has never been fixed? Hope someone can give me more information here as it is very frustrating.Please do read the OP for more information. It is the exact same problem that I am having.
On Wednesday, January 17, 2018 at 11:23:18 PM UTC+1, Kevin Marsh wrote:I'm trying to get a dump of a Postgres database while avoiding several large tables. I've tried several methods to specify certain only tables, as the docs seem to say you should be able to. I've tried:
- gcloud sql instances export db-foo gs://db-backups/$(date +%s)-sql.gz --database foo_production -t leads,issues (only exported leads)
- gcloud sql instances export db-foo gs://db-backups/$(date +%s)-sql.gz --database foo_production -t leads -t issues (only exported issues)
- gcloud sql instances export db-foo gs://db-backups/$(date +%s)-sql.gz --database foo_production --table=leads,
issues (only exported leads) Is anyone else having this 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/7dacc9a8-5509-476d-b2da-d7186a6d9b18o%40googlegroups.com.
No comments:
Post a Comment