Extension request: timescaledb [64602105]

Assigned

Feature Request

Status Update

No update yet.

Description

ch...@frostly.com

created issue #1

Aug 11, 2017 04:46PM

Hi, I would like to request the addition of the timescaledb postgres extension (

https://github.com/timescale/timescaledb) for storing timeseries data in Cloud SQL.

Comments

na...@google.com <na...@google.com> #2Aug 11, 2017 07:30PM

Assigned to gc...@google.com.

Thanks for submitting request.

I have forwarded this feature request to the CloudSQL product management team. You can track this thread to post any further comments or check the updates regarding this feature request. However we can't provide you with any ETA or guarantee it's implementation.

pa...@gmail.com <pa...@gmail.com> #3Nov 2, 2017 10:31AM

This would be useful to me as well, allow a move from our own postgres+timescale setup to using Cloud SQL.

gr...@fiskekroken.org <gr...@fiskekroken.org> #4Nov 10, 2017 08:08AM

Me too!

For small to medium size IoT applications (and other time series applications) it's a real killer application, especially in combination with PostGIS (which is already supported on Cloud SQL).

ha...@oden.io <ha...@oden.io> #5Nov 15, 2017 11:54PM

This would be huge. I think I speak for all engineers at our company when I say we're looking forward to try it out when it becomes available

Message last modified on Nov 15, 2017 11:54PM

wi...@gmail.com <wi...@gmail.com> #6Nov 19, 2017 10:51AM

This would be an amazing addition for GCP. Please add.

lo...@gmail.com <lo...@gmail.com> #7Nov 26, 2017 09:18PM

Awesome. I will absolutely switch to Cloud SQL if GCP support TimescaleDB. Currently, I still have to use the self-hosted solution on GCP.

ca...@gmail.com <ca...@gmail.com> #8Nov 27, 2017 03:27PM

Me too!

mt...@gmail.com <mt...@gmail.com> #9Dec 21, 2017 07:23PM

Please do make this available. Would use GCP over AWS.

[Deleted User] <[Deleted User]> #10Jan 2, 2018 11:51PM

This would be so very nice! I would love to be able to move this part of our on prem solution into GCP as well...

[Deleted User] <[Deleted User]> #11Jan 23, 2018 01:22PM

Me, too!

[Deleted User] <[Deleted User]> #12Jan 24, 2018 11:05AM

dp...@brightgate.com <dp...@brightgate.com> #13Jan 24, 2018 07:51PM

Also interested. This would complement Cloud IoT Core very nicely.

[Deleted User] <[Deleted User]> #14Jan 25, 2018 11:43PM

ME TOO!

je...@gmail.com <je...@gmail.com> #15Jan 27, 2018 01:03AM

ch...@contentthread.com <ch...@contentthread.com> #16Jan 27, 2018 01:30PM

[Deleted User] <[Deleted User]> #17Jan 30, 2018 03:11AM

Me, too!

mi...@gmail.com <mi...@gmail.com> #18Jan 30, 2018 10:40PM

Me, too!

my...@gmail.com <my...@gmail.com> #19Feb 7, 2018 07:17PM

Me too

ne...@gmail.com <ne...@gmail.com> #20Feb 12, 2018 12:22AM

Me too!

ba...@bad.so <ba...@bad.so> #21Feb 17, 2018 03:32PM

br...@gmail.com <br...@gmail.com> #22Feb 21, 2018 11:28AM

da...@diit.ca <da...@diit.ca> #23Feb 22, 2018 05:33PM

rn...@gmail.com <rn...@gmail.com> #24Mar 3, 2018 01:37AM

Me too

sk...@gmail.com <sk...@gmail.com> #25Mar 4, 2018 02:25AM

ba...@bad.so <ba...@bad.so> #26Mar 5, 2018 04:19AM

jo...@midnightlinux.com <jo...@midnightlinux.com> #27Mar 5, 2018 04:59AM

I hope everyone replying +1 is also clicking the star to the left of 'Extension request: timescaledb'. Stars are easier to gauge interest compared to replies.

an...@mirusresearch.com <an...@mirusresearch.com> #28Mar 8, 2018 02:31PM

Add my company to the list - already moving everything to GKE & GCP, would love to migrate timeseries jobs to Cloud SQL

[Deleted User] <[Deleted User]> #29Mar 14, 2018 11:36AM

sr...@gmail.com <sr...@gmail.com> #30Mar 15, 2018 10:19AM

+1 After implementing this I would see no reason to use any other database solution. It would basically cover all the use cases of NoSQL but with sweet, sweet Postgres features and Cloud SQL maintenance

nf...@gmail.com <nf...@gmail.com> #31Mar 15, 2018 01:30PM

+1 Me too!

un...@gmail.com <un...@gmail.com> #32Mar 20, 2018 08:49PM

+1 Me too

cw...@gmail.com <cw...@gmail.com> #33Mar 22, 2018 04:07PM

Me, too!

ja...@jargonia.co.uk <ja...@jargonia.co.uk> #34Mar 22, 2018 04:07PM

+1 Me too

al...@mirusresearch.com <al...@mirusresearch.com> #35Mar 23, 2018 02:41AM

ga...@gmail.com <ga...@gmail.com> #36Mar 23, 2018 10:09AM

a....@convotis.com <a....@convotis.com> #37Mar 23, 2018 11:22AM

+1, could start using Cloud SQL instead of Postgres Timescale containers in streaming replication with repmgr + pgpool and a bunch of scripts to handle several edge cases...

ac...@nes.ru <ac...@nes.ru> #38Mar 25, 2018 12:33AM

ar...@gmail.com <ar...@gmail.com> #39Mar 31, 2018 09:45AM

as...@gmail.com <as...@gmail.com> #40Apr 1, 2018 02:20AM

[Deleted User] <[Deleted User]> #41Apr 4, 2018 09:54AM

Yep! Prometheus in GKE just asking for it! +1

[Deleted User] <[Deleted User]> #42Apr 4, 2018 11:34AM

[Deleted User] <[Deleted User]> #43Apr 11, 2018 11:54AM

Me, too!

b....@gmail.com <b....@gmail.com> #44Apr 14, 2018 12:15PM

ab...@amperon.co <ab...@amperon.co> #45Apr 16, 2018 02:37AM

aj...@google.com <aj...@google.com> #46Apr 17, 2018 05:58PM

da...@we-riot.com <da...@we-riot.com> #47Apr 18, 2018 09:41PM

yes please

jm...@gmail.com <jm...@gmail.com> #48Apr 19, 2018 08:30PM

ko...@gmail.com <ko...@gmail.com> #49Apr 19, 2018 11:51PM

os...@aiven.io <os...@aiven.io> #50Apr 20, 2018 10:55AM

It's not Cloud SQL, but you can use TimescaleDB on a managed PostgreSQL service in GCP through Aiven:

https://console.cloud.google.com/launcher/details/aiven-saas/aiven-postgresql

[Deleted User] <[Deleted User]> #51Apr 23, 2018 07:00PM

to...@nytimes.com <to...@nytimes.com> #52Apr 24, 2018 05:25PM

There is also a separate ticket for the pg_prometheus extension for people who are subscribed for the prometheus use-case:

https://issuetracker.google.com/issues/77537715
I would recommend subscribing to that one too.

Reminder: "star" an issue to show interest.

Message last modified on Apr 24, 2018 05:27PM

la...@fluxon.com <la...@fluxon.com> #53Apr 26, 2018 05:00PM

+1 I would love to see this in CloudSQL.

wi...@gmail.com <wi...@gmail.com> #54Apr 29, 2018 02:42PM

hu...@gmail.com <hu...@gmail.com> #55May 3, 2018 03:45AM

+1, Me too!

ma...@forestrock.co.uk <ma...@forestrock.co.uk> #56May 3, 2018 11:43AM

+1 we would like this extension

po...@gmail.com <po...@gmail.com> #57May 6, 2018 12:09PM

cl...@zen.ly <cl...@zen.ly> #58May 9, 2018 09:51AM

+1 with pg_prometheus extension too (

https://issuetracker.google.com/issues/77537715)

cs...@gmail.com <cs...@gmail.com> #59May 9, 2018 10:22AM

[Deleted User] <[Deleted User]> #60May 9, 2018 11:49AM

sr...@gmail.com <sr...@gmail.com> #61May 9, 2018 08:21PM

tw...@gmail.com <tw...@gmail.com> #62May 14, 2018 06:01PM

[Deleted User] <[Deleted User]> #63May 21, 2018 07:25PM

jo...@gmail.com <jo...@gmail.com> #64May 22, 2018 06:12PM

co...@gmail.com <co...@gmail.com> #65May 24, 2018 08:30AM

This would mean our company can move databases from kubernetes to a managed database, highly valuable. Can we get a progress report on this?

hr...@gmail.com <hr...@gmail.com> #66May 26, 2018 07:42AM

need to install tds_fdw extension, can you help he with this permission

ma...@gmail.com <ma...@gmail.com> #67Jun 2, 2018 10:52AM

I'm also interested in this.

ra...@trueanthem.com <ra...@trueanthem.com> #68Jun 3, 2018 02:47PM

ja...@expeditors.com <ja...@expeditors.com> #69Jun 4, 2018 02:22PM

This would be a fantastic feature to see implemented!

gu...@magic-carpet.ch <gu...@magic-carpet.ch> #70Jun 6, 2018 07:41AM

+1 look forward to it. Currently with AWS but would switch to GCP is this feature was available

As...@ashtonkinslow.com <As...@ashtonkinslow.com> #71Jun 10, 2018 07:25AM

dy...@gmail.com <dy...@gmail.com> #72Jun 12, 2018 04:51AM

[Deleted User] <[Deleted User]> #73Jun 12, 2018 08:29AM

[Deleted User] <[Deleted User]> #74Jun 12, 2018 10:18AM

[Deleted User] <[Deleted User]> #75Jun 13, 2018 01:27PM

Me too

sh...@gmail.com <sh...@gmail.com> #76Jun 14, 2018 06:23AM

Me, too!

to...@gmail.com <to...@gmail.com> #77Jun 15, 2018 02:28PM

ke...@smackhigh.com <ke...@smackhigh.com> #78Jun 19, 2018 02:36AM

th...@gmail.com <th...@gmail.com> #79Jun 20, 2018 08:08AM

ti...@solarmonkey.nl <ti...@solarmonkey.nl> #80Jun 20, 2018 08:18AM

ba...@bad.so <ba...@bad.so> #81Jun 20, 2018 11:56AM

km...@gmail.com <km...@gmail.com> #82Jun 26, 2018 06:08PM

[Deleted User] <[Deleted User]> #83Jun 30, 2018 01:44AM

+1 really interested

dh...@gmail.com <dh...@gmail.com> #84Jul 2, 2018 07:39PM

+1 please!

to...@nytimes.com <to...@nytimes.com> #85Jul 2, 2018 07:50PM

This is an aside, but in case anyone's use case was for long-term prometheus metrics storage and can't wait for the extension to get integrated, take a look at

https://github.com/improbable-eng/thanos, which doesn't require the use of PostgreSQL.

fb...@gmail.com <fb...@gmail.com> #86Jul 8, 2018 08:05PM

+1 Me Too!

sg...@gmail.com <sg...@gmail.com> #87Jul 8, 2018 10:35PM

[Deleted User] <[Deleted User]> #88Jul 9, 2018 02:13PM

Me too!

wi...@redbrain.com <wi...@redbrain.com> #89Jul 10, 2018 12:47PM

+1 Me Too!

ti...@solarmonkey.nl <ti...@solarmonkey.nl> #90Jul 10, 2018 03:07PM

Please STAR this issue instead of adding "+1" replies as that creates a notification email for everyone who has starred...

[Deleted User] <[Deleted User]> #91Jul 26, 2018 01:50PM

[Deleted User] <[Deleted User]> #92Jul 26, 2018 02:11PM

Me Too!

fi...@voiapp.io <fi...@voiapp.io> #93Jul 26, 2018 07:12PM

+1 +1 +1

sr...@gmail.com <sr...@gmail.com> #94Jul 26, 2018 07:17PM

+1
+1
+1

ge...@compound.finance <ge...@compound.finance> #95Jul 26, 2018 10:12PM

[Deleted User] <[Deleted User]> #96Jul 26, 2018 10:38PM

al...@gmail.com <al...@gmail.com> #97Jul 27, 2018 04:17AM

[Deleted User] <[Deleted User]> #98Jul 27, 2018 07:49AM

mo...@gmail.com <mo...@gmail.com> #99Jul 29, 2018 09:28AM

th...@gmail.com <th...@gmail.com> #100Jul 29, 2018 02:14PM

ni...@gmail.com <ni...@gmail.com> #101Aug 2, 2018 09:09PM

da...@we-riot.com <da...@we-riot.com> #102Aug 10, 2018 09:25AM

is it happening?

al...@gmail.com <al...@gmail.com> #103Aug 10, 2018 06:26PM

Me too!

ka...@gmail.com <ka...@gmail.com> #104Aug 11, 2018 01:27AM

wa...@gmail.com <wa...@gmail.com> #105Aug 14, 2018 02:00AM

[Deleted User] <[Deleted User]> #106Aug 15, 2018 04:12PM

[Deleted User] <[Deleted User]> #107Aug 15, 2018 06:51PM

[Deleted User] <[Deleted User]> #108Aug 22, 2018 12:22PM

ch...@gmail.com <ch...@gmail.com> #109Sep 7, 2018 12:27PM

br...@gmail.com <br...@gmail.com> #110Sep 7, 2018 03:30PM

[Deleted User] <[Deleted User]> #111Sep 12, 2018 03:24AM

me...@imubit.com <me...@imubit.com> #112Sep 17, 2018 04:36PM

ga...@gmail.com <ga...@gmail.com> #113Sep 18, 2018 09:07PM

bt...@gmail.com <bt...@gmail.com> #114Sep 20, 2018 01:47AM

[Deleted User] <[Deleted User]> #115Oct 1, 2018 06:08PM

[Deleted User] <[Deleted User]> #116Oct 6, 2018 01:42PM

[Deleted User] <[Deleted User]> #117Oct 11, 2018 09:45AM

da...@elder.org <da...@elder.org> #118Oct 12, 2018 02:32PM

[Deleted User] <[Deleted User]> #119Oct 12, 2018 02:34PM

This would be a game changer for us, +1

pd...@hackerone.com <pd...@hackerone.com> #120Oct 13, 2018 05:31PM

deleted

Message last modified on Oct 15, 2018 05:58PM

as...@gmail.com <as...@gmail.com> #121Oct 15, 2018 10:54AM

[Deleted User] <[Deleted User]> #122Oct 24, 2018 02:53AM

jo...@cylera.com <jo...@cylera.com> #123Oct 26, 2018 06:19PM

[Deleted User] <[Deleted User]> #124Oct 26, 2018 06:55PM

bj...@gmail.com <bj...@gmail.com> #125Oct 28, 2018 11:13AM

eu...@strg.at <eu...@strg.at> #126Oct 29, 2018 12:09PM

ga...@gmail.com <ga...@gmail.com> #127Oct 29, 2018 03:22PM

de...@dspa.in <de...@dspa.in> #128Nov 2, 2018 02:35AM

+1 🦄

[Deleted User] <[Deleted User]> #129Nov 2, 2018 06:34PM

li...@gmail.com <li...@gmail.com> #130Nov 4, 2018 04:42PM

ma...@gmail.com <ma...@gmail.com> #131Nov 9, 2018 09:49AM

g....@gmail.com <g....@gmail.com> #132Nov 9, 2018 11:30AM

mi...@gmail.com <mi...@gmail.com> #133Nov 10, 2018 11:57AM

ha...@gmail.com <ha...@gmail.com> #134Nov 10, 2018 10:52PM

+20

ke...@gmail.com <ke...@gmail.com> #135Nov 14, 2018 08:15PM

What is the status of this?

ru...@gmail.com <ru...@gmail.com> #136Nov 25, 2018 09:21PM

ro...@gmail.com <ro...@gmail.com> #137Nov 26, 2018 10:43AM

It's been a year now. It should be very easy to integrate this extension, but Google won't do it for as long as they can to keep selling their completely overpriced BigTable and Spanner products.
Our company has moved all our DB hosting to Aiven now, as they support TimescaleDB.

in...@goottics.com <in...@goottics.com> #138Nov 27, 2018 05:56PM

Me too!

oe...@gmail.com <oe...@gmail.com> #139Nov 28, 2018 03:12PM

Me, too!

m....@gmail.com <m....@gmail.com> #140Nov 28, 2018 04:58PM

Me too!

ks...@gmail.com <ks...@gmail.com> #141Nov 30, 2018 09:26AM

ri...@localistico.com <ri...@localistico.com> #142Dec 3, 2018 01:10PM

+1 - come on, Google team!

pe...@open-cosmos.com <pe...@open-cosmos.com> #143Dec 4, 2018 10:24AM

vo...@ottogroup.com <vo...@ottogroup.com> #144Dec 4, 2018 01:23PM

wr...@gmail.com <wr...@gmail.com> #145Dec 5, 2018 06:39AM

[Deleted User] <[Deleted User]> #146Dec 6, 2018 10:39AM

jo...@omnyhealth.com <jo...@omnyhealth.com> #147Dec 6, 2018 04:29PM

[Deleted User] <[Deleted User]> #148Dec 13, 2018 10:16AM

ro...@storemaven.com <ro...@storemaven.com> #149Dec 13, 2018 01:50PM

[Deleted User] <[Deleted User]> #150Dec 13, 2018 04:32PM

[Deleted User] <[Deleted User]> #151Dec 13, 2018 04:49PM

ne...@gmail.com <ne...@gmail.com> #152Dec 14, 2018 10:51AM

I am also interested in this integration.

re...@gmail.com <re...@gmail.com> #153Dec 14, 2018 10:31PM

sh...@gmail.com <sh...@gmail.com> #154Dec 16, 2018 09:14AM

[Deleted User] <[Deleted User]> #155Dec 20, 2018 02:07PM

ph...@gmail.com <ph...@gmail.com> #156Dec 28, 2018 04:21AM

+1 MeToo!

co...@gmail.com <co...@gmail.com> #157Jan 4, 2019 01:18AM

+1 please!

Also, are there any updates on this?

ke...@gmail.com <ke...@gmail.com> #158Jan 4, 2019 04:48AM

Message last modified on Jan 23, 2019 07:14PM

[Deleted User] <[Deleted User]> #159Jan 4, 2019 01:59PM

How do you mean? It sounds like they'd like this integration. Here's an issue about it:

https://github.com/timescale/timescaledb/issues/65

ma...@gmail.com <ma...@gmail.com> #160Jan 4, 2019 02:20PM

The github issue is a bit old but they changed their licensing model recently like many other companies

https://blog.timescale.com/how-we-are-building-an-open-source-business-a7701516a480

i....@gmail.com <i....@gmail.com> #161Jan 14, 2019 11:16AM

TSDB is licensed under Apache. How does that prevent Google from including it as an extension?

sw...@gmail.com <sw...@gmail.com> #162Jan 21, 2019 03:30PM

th...@gmail.com <th...@gmail.com> #163Jan 21, 2019 03:30PM

[Deleted User] <[Deleted User]> #164Jan 21, 2019 03:52PM

to...@springernature.com <to...@springernature.com> #165Jan 23, 2019 05:20PM

da...@springer.com <da...@springer.com> #166Jan 23, 2019 05:22PM

to...@lmit.pt <to...@lmit.pt> #167Jan 24, 2019 06:44PM

cl...@gmail.com <cl...@gmail.com> #168Jan 25, 2019 12:33AM

lu...@gmail.com <lu...@gmail.com> #169Jan 25, 2019 03:24PM

me...@gmail.com <me...@gmail.com> #170Jan 26, 2019 06:09AM

ki...@gmail.com <ki...@gmail.com> #171Jan 30, 2019 07:22AM

du...@gmail.com <du...@gmail.com> #172Feb 1, 2019 08:13AM

Me too!

jo...@gmail.com <jo...@gmail.com> #173Feb 7, 2019 08:18AM

le...@gmail.com <le...@gmail.com> #174Feb 8, 2019 01:37AM

+1. Please, make it happen google.

gm...@gmail.com <gm...@gmail.com> #175Feb 12, 2019 02:47PM

ag...@gmail.com <ag...@gmail.com> #176Feb 14, 2019 05:50AM

Mee too!

[Deleted User] <[Deleted User]> #177Feb 15, 2019 01:29AM

Me too!

ka...@autotrader.co.uk <ka...@autotrader.co.uk> #178Feb 19, 2019 07:42AM

+100

tr...@gmail.com <tr...@gmail.com> #179Feb 19, 2019 10:09PM

ka...@4ware.net <ka...@4ware.net> #180Feb 20, 2019 11:20AM

ta...@gmail.com <ta...@gmail.com> #181Feb 25, 2019 11:15AM

[Deleted User] <[Deleted User]> #182Feb 25, 2019 11:16PM

ja...@oden.io <ja...@oden.io> #183Feb 26, 2019 05:39AM

ha...@gmail.com <ha...@gmail.com> #184Feb 26, 2019 08:42AM

[Deleted User] <[Deleted User]> #185Feb 28, 2019 01:55PM

cl...@gmail.com <cl...@gmail.com> #186Mar 1, 2019 07:26PM

No movement on this google??? come onnnn

an...@gmail.com <an...@gmail.com> #187Mar 8, 2019 04:37AM

Me, too!

mi...@pocorschi.com <mi...@pocorschi.com> #188Mar 8, 2019 10:18PM

[Deleted User] <[Deleted User]> #189Mar 10, 2019 05:51PM

ef...@sensencall.com <ef...@sensencall.com> #190Mar 12, 2019 02:22PM

[Deleted User] <[Deleted User]> #191Mar 16, 2019 08:51AM

aa...@gmail.com <aa...@gmail.com> #192Mar 17, 2019 10:05PM

ke...@gmail.com <ke...@gmail.com> #193Mar 18, 2019 04:18PM

le...@gmail.com <le...@gmail.com> #194Mar 18, 2019 07:23PM

al...@gmail.com <al...@gmail.com> #195Mar 19, 2019 12:52AM

Azure just announced this feature:

https://blog.timescale.com/timescale-microsoft-azure-team-up-to-power-iot-and-time-series-workloads/

na...@gmail.com <na...@gmail.com> #196Mar 26, 2019 12:49PM

[Deleted User] <[Deleted User]> #197Mar 26, 2019 12:50PM

Me, too!

st...@ukubu.com <st...@ukubu.com> #198Mar 26, 2019 03:11PM

Me, too!

[Deleted User] <[Deleted User]> #199Mar 26, 2019 06:58PM

cl...@gmail.com <cl...@gmail.com> #200Mar 29, 2019 06:23PM

ja...@avalonsolutions.com <ja...@avalonsolutions.com> #201Apr 3, 2019 08:10AM

Me, too!

[Deleted User] <[Deleted User]> #202Apr 4, 2019 03:23PM

ha...@gmail.com <ha...@gmail.com> #203Apr 12, 2019 05:12PM

sc...@gmail.com <sc...@gmail.com> #204Apr 19, 2019 03:39PM

jo...@gmail.com <jo...@gmail.com> #205Apr 23, 2019 07:27AM

Heavily used at my company. We would switch to Cloud SQL immediately.

[Deleted User] <[Deleted User]> #206Apr 23, 2019 08:07PM

al...@dsol.com.br <al...@dsol.com.br> #207Apr 24, 2019 04:31PM

+1 Me Too!

da...@gmail.com <da...@gmail.com> #208Apr 24, 2019 06:05PM

[Deleted User] <[Deleted User]> #209Apr 24, 2019 06:07PM

Note that you should use "star" button instead of adding +1 comments here. Every comment generates spam email to all the staring people and only way to get away of this spam is to come and remove star. So every comment removes stars and downvotes the issue.

If you really have big time series (timescaledb) then google wants you to use their better service BigQuery, not CloudSQL.

ar...@gmail.com <ar...@gmail.com> #210May 2, 2019 01:20PM

ne...@gmail.com <ne...@gmail.com> #211May 8, 2019 08:40PM

me too

02...@gmail.com <02...@gmail.com> #212May 13, 2019 03:16PM

[Deleted User] <[Deleted User]> #213May 15, 2019 05:56PM

bl...@gmail.com <bl...@gmail.com> #214May 25, 2019 06:34PM

+1

>> If you really have big time series (timescaledb) then google wants you to use their better service
>> BigQuery, not CloudSQL.

Incorrect. BigQuery is built for BI (latency is bad even with dedicated slots). If you want a time series for generating customer facing visualizations TimeScale is the correct solution.

Message last modified on May 26, 2019 07:53PM

jp...@izinto.cloud <jp...@izinto.cloud> #215May 29, 2019 09:24AM

pa...@gmail.com <pa...@gmail.com> #216May 30, 2019 06:56AM

je...@gmail.com <je...@gmail.com> #217May 30, 2019 10:32PM

MeToo! +1 Please add. This would be amazing

gr...@gmail.com <gr...@gmail.com> #218May 31, 2019 05:32PM

This is already available on Azure:

https://azure.microsoft.com/en-us/blog/power-iot-and-time-series-workloads-with-timescaledb-for-azure-database-for-postgresql/
Come on GCP, don't get left behind on this too...

an...@gmail.com <an...@gmail.com> #219Jun 16, 2019 07:53AM

[Deleted User] <[Deleted User]> #220Jun 18, 2019 03:40PM

[Deleted User] <[Deleted User]> #221Jun 19, 2019 08:02PM

zd...@exponea.com <zd...@exponea.com> #222Jun 28, 2019 12:58PM

[Deleted User] <[Deleted User]> #223Jun 28, 2019 02:02PM

pe...@open-cosmos.com <pe...@open-cosmos.com> #224Jul 3, 2019 08:18AM

[Deleted User] <[Deleted User]> #225Jul 8, 2019 06:49PM

ka...@4ware.net <ka...@4ware.net> #226Jul 9, 2019 10:11AM

ad...@iterate.no <ad...@iterate.no> #227Jul 11, 2019 02:53PM

[Deleted User] <[Deleted User]> #228Jul 18, 2019 10:56AM

[Deleted User] <[Deleted User]> #229Jul 18, 2019 11:00AM

come on Google, do something!

ne...@gmail.com <ne...@gmail.com> #230Jul 19, 2019 09:58AM

+ 1 how many votes do you need to implement it? When we can expect it?

jo...@descarteslabs.com <jo...@descarteslabs.com> #231Jul 19, 2019 04:51PM

[Deleted User] <[Deleted User]> #232Jul 22, 2019 06:22AM

guys, press a `star` icon to increase vote count

cl...@gmail.com <cl...@gmail.com> #233Jul 23, 2019 03:49PM

coming up on 2 years now... can we at least get an update?

ha...@gmail.com <ha...@gmail.com> #234Jul 24, 2019 01:33AM

Me too!

[Deleted User] <[Deleted User]> #235Jul 24, 2019 02:51PM

Me, too!

Message last modified on Jul 24, 2019 02:52PM

mn...@flexport.com <mn...@flexport.com> #236Jul 24, 2019 03:16PM

A reminder: the only number that counts is the number of people who have star'd this request. That's the star immediately to the left of the title and number of this issue, up above. Adding a "+1" doesn't show up on anyone's reports.

ca...@gmail.com <ca...@gmail.com> #237Aug 4, 2019 01:42PM

I have used influx for time series data in the past, but I need to work with both time series and non time series data. This posgres plugin is perfect.
Hopefully, GCP Cloud SQL or AWS RDS could add support for this. I have starred as suggested.

bz...@gmail.com <bz...@gmail.com> #238Aug 8, 2019 11:24AM

am...@google.com <am...@google.com> #239Aug 8, 2019 11:36AM

All,

Please remember to upvote at the top of the thread
There are 238 comments but only 174 upvotes at this point

[Deleted User] <[Deleted User]> #240Aug 13, 2019 11:00AM

mi...@pocorschi.com <mi...@pocorschi.com> #241Aug 19, 2019 02:53PM

ra...@gmail.com <ra...@gmail.com> #242Aug 21, 2019 10:05PM

ch...@gmail.com <ch...@gmail.com> #243Aug 23, 2019 06:05PM

[Deleted User] <[Deleted User]> #244Sep 17, 2019 03:40PM

really need this, the tool is awesome

ka...@gmail.com <ka...@gmail.com> #245Sep 24, 2019 05:40PM

Remember to star instead of +1

Message last modified on Sep 24, 2019 05:41PM

ja...@gmail.com <ja...@gmail.com> #246Sep 24, 2019 06:12PM

ne...@gmail.com <ne...@gmail.com> #247Oct 15, 2019 09:31AM

ja...@netapp.com <ja...@netapp.com> #248Oct 17, 2019 05:12PM

Any news or ETA about this?

hu...@gmail.com <hu...@gmail.com> #249Oct 29, 2019 01:14AM

st...@gmail.com <st...@gmail.com> #250Oct 29, 2019 03:17AM

no...@gmail.com <no...@gmail.com> #251Nov 4, 2019 06:55PM

be...@benmorgan.io <be...@benmorgan.io> #252Nov 5, 2019 08:19PM

ki...@gmail.com <ki...@gmail.com> #253Nov 24, 2019 11:24AM

Me, too! +1 I think this would be a good combination of PostgreSQL features and a columnar like store. Hopefully you'll find a way to add this extension in a way that fits together with the roadmap of other columnar/timeseries offerings :)

th...@mirakl.com <th...@mirakl.com> #254Dec 2, 2019 10:55AM

th...@mirakl.com <th...@mirakl.com> #255Dec 2, 2019 10:55AM

Duplicate entry

Message last modified on Dec 2, 2019 10:56AM

in...@synthetica.ai <in...@synthetica.ai> #256Dec 3, 2019 11:19AM

sa...@loblaw.ca <sa...@loblaw.ca> #257Dec 9, 2019 10:07PM

ry...@radious.co <ry...@radious.co> #258Dec 26, 2019 05:25AM

Me too!

jo...@expeditors.com <jo...@expeditors.com> #259Jan 2, 2020 11:07AM

Yes starred need this

ph...@gmail.com <ph...@gmail.com> #260Jan 2, 2020 03:56PM

pa...@gmail.com <pa...@gmail.com> #261Jan 5, 2020 02:39PM

dd...@gmail.com <dd...@gmail.com> #262Jan 6, 2020 06:41PM

jo...@gmail.com <jo...@gmail.com> #263Jan 21, 2020 07:23PM

[Deleted User] <[Deleted User]> #264Jan 23, 2020 10:14PM

df...@imagemfilmes.com.br <df...@imagemfilmes.com.br> #265Jan 28, 2020 12:20PM

jb...@gmail.com <jb...@gmail.com> #266Jan 29, 2020 02:27AM

vm...@gmail.com <vm...@gmail.com> #267Feb 19, 2020 07:37AM

Me, too!

[Deleted User] <[Deleted User]> #268Feb 21, 2020 05:49PM

do...@mattel.com <do...@mattel.com> #269Mar 2, 2020 08:24PM

vf...@justeattakeaway.com <vf...@justeattakeaway.com> #270Mar 3, 2020 05:33PM

[Deleted User] <[Deleted User]> #271Mar 12, 2020 12:54AM

ni...@gmail.com <ni...@gmail.com> #272Mar 17, 2020 02:53AM

@google. Kindly explain the nature of the blocking issue so that the community can understand if this feature won't be implemented by Google. It is understandable if the nature of the issue cannot be discussed publicly but feedback on this public issue based on the internal issue would be greatly appreciated. If the internal issue blocking this feature request cannot or will not be fixed, it would be great if the team lets the community know.

ni...@gmail.com <ni...@gmail.com> #273Mar 18, 2020 04:30PM

ec...@gmail.com <ec...@gmail.com> #274Apr 3, 2020 09:18PM

kh...@gmail.com <kh...@gmail.com> #275Apr 5, 2020 03:34PM

me too!

Message last modified on Apr 5, 2020 03:37PM

sh...@gmail.com <sh...@gmail.com> #276Apr 6, 2020 12:30PM

ro...@liveperson.com <ro...@liveperson.com> #277Apr 16, 2020 09:25AM

se...@gmail.com <se...@gmail.com> #278Apr 16, 2020 03:18PM

na...@pixelauthority.com <na...@pixelauthority.com> #279Apr 22, 2020 02:55PM

ni...@nicehash.com <ni...@nicehash.com> #280Apr 30, 2020 07:59AM

bl...@gmail.com <bl...@gmail.com> #281May 14, 2020 04:08AM

[Deleted User] <[Deleted User]> #282May 16, 2020 04:56AM

+1 Would be amazing for us! Please add

Message last modified on May 16, 2020 04:57AM

ro...@gmail.com <ro...@gmail.com> #283May 16, 2020 12:27PM

ma...@gmail.com <ma...@gmail.com> #284May 16, 2020 02:21PM

+1 if that helps :)

je...@ampcontrolgroup.com <je...@ampcontrolgroup.com> #285May 20, 2020 02:50AM

+1. Is Google Cloud working on a Time series database?

ra...@gmail.com <ra...@gmail.com> #286May 20, 2020 03:12PM

+ 1. Me too!

fa...@gmail.com <fa...@gmail.com> #287May 21, 2020 05:02PM

I would also like to request this.

[Deleted User] <[Deleted User]> #288May 21, 2020 05:23PM

[Deleted User] <[Deleted User]> #289May 22, 2020 04:24PM

Timescale (

timescale.com) has the timescaledb extension licensed such that cloud providers cannot offer TimescaleDB as a service:

https://www.timescale.com/legal/licenses. For anyone following this thread, do not get your hopes up about this being offered because it appears Google is legally not allowed to. @google should acknowledge this though and close the feature request, but they can't even seem to do that.

ya...@gmail.com <ya...@gmail.com> #290Jun 22, 2020 07:10PM

Please support this! Alibaba Cloud offered the open-source version,

https://www.alibabacloud.com/help/doc-detail/118899.htm?spm=a2c63.p38356.b99.416.1aa6441ajnHKlF.

[Deleted User] <[Deleted User]> #291Jun 23, 2020 02:43AM

So Azure and Alibaba support it. License is not a prohibiting factor, if you partner with the organization producing the product like Azure did

aa...@gmail.com <aa...@gmail.com> #292Jun 30, 2020 03:28AM

aa...@gmail.com <aa...@gmail.com> #293Jun 30, 2020 03:38AM

Please support this! This is critical to our workflow!

pr...@gmail.com <pr...@gmail.com> #294Jul 2, 2020 06:39PM

+1 , would like this as well!

pa...@gmail.com <pa...@gmail.com> #295Jul 6, 2020 11:02AM

l....@gmail.com <l....@gmail.com> #296Jul 26, 2020 08:44PM

+1!!!!

ar...@dka.io <ar...@dka.io> #297Aug 6, 2020 09:22AM

+1!

aj...@timescale.com <aj...@timescale.com> #298Aug 27, 2020 05:37AM

For everyone tracking this issue, fully managed PostgreSQL + TimescaleDB is now available on GCP (and Azure, and AWS, across 76 regions), via Timescale Cloud:

https://www.timescale.com/cloud-choose

[Deleted User] <[Deleted User]> #299Sep 11, 2020 02:42PM

nc...@brightcove.com <nc...@brightcove.com> #300Sep 12, 2020 03:04PM

se...@gmail.com <se...@gmail.com> #301Sep 18, 2020 05:13AM

vf...@justeattakeaway.com <vf...@justeattakeaway.com> #302Sep 22, 2020 04:14PM

ju...@gmail.com <ju...@gmail.com> #303Sep 28, 2020 10:01AM

[Deleted User] <[Deleted User]> #304Oct 8, 2020 05:53AM

+1 Me too!

[Deleted User] <[Deleted User]> #305Oct 13, 2020 04:04PM

+1 Me too!

ch...@gmail.com <ch...@gmail.com> #306Oct 18, 2020 03:01PM

+1 Me too!

rh...@gmail.com <rh...@gmail.com> #307Oct 19, 2020 09:22PM

lo...@gmail.com <lo...@gmail.com> #308Oct 21, 2020 11:37AM

ja...@gmail.com <ja...@gmail.com> #309Oct 30, 2020 01:00AM

je...@gmail.com <je...@gmail.com> #310Nov 4, 2020 04:26PM

al...@altenar.com <al...@altenar.com> #311Nov 19, 2020 09:41AM

+1 please

gr...@basefarm.com <gr...@basefarm.com> #312Nov 19, 2020 10:03AM

Managed PostgreSQL on Azure have support for this extension, for me this will have an impact when recommending platform for small to medium scale IoT applications.

So Google, please add support for this extension!

du...@google.com <du...@google.com> #313Nov 27, 2020 04:42PM

+1 a customer is selecting cloud vendors (GCP, AWS and Azure) and request for this feature as one of the evaluation critieria.

ke...@google.com <ke...@google.com> #314Dec 16, 2020 02:19PM

+1, had customer request this today.

ya...@gmail.com <ya...@gmail.com> #315Dec 16, 2020 11:13PM

3 years later. Still no support from google?

Message last modified on Dec 16, 2020 11:18PM

sa...@skylo.tech <sa...@skylo.tech> #316Dec 29, 2020 12:39AM

sw...@leftbin.com <sw...@leftbin.com> #317Jan 4, 2021 09:18AM

please add this extension to cloudsql.

ke...@gmail.com <ke...@gmail.com> #318Feb 4, 2021 03:52AM

ry...@theleaguestock.com <ry...@theleaguestock.com> #319Feb 6, 2021 05:04PM

ho...@gmail.com <ho...@gmail.com> #320Feb 10, 2021 01:38PM

th...@gmail.com <th...@gmail.com> #321Feb 21, 2021 03:18PM

ch...@entropealabs.com <ch...@entropealabs.com> #322Mar 1, 2021 08:09PM

ra...@ras.wtf <ra...@ras.wtf> #323Mar 22, 2021 06:30PM

le...@g3i.com.au <le...@g3i.com.au> #324Mar 27, 2021 01:29AM

What is the status of this feature? AzureDB has got support for this extension for some time now.

co...@gmail.com <co...@gmail.com> #325Apr 15, 2021 07:50PM

cl...@skylo.dev <cl...@skylo.dev> #326Apr 15, 2021 10:13PM

Is it possible to provide an ETA for this feature?

pr...@gmail.com <pr...@gmail.com> #327Apr 30, 2021 03:05PM

Comment has been deleted.

Message last modified on Apr 30, 2021 03:05PM

[Deleted User] <[Deleted User]> #328Apr 30, 2021 03:06PM

We would love to use this for our billing metrics

[Deleted User] <[Deleted User]> #329May 6, 2021 08:44AM

hu...@gmail.com <hu...@gmail.com> #330Jun 8, 2021 03:29PM

[Deleted User] <[Deleted User]> #331Jun 9, 2021 08:44PM

ma...@gmail.com <ma...@gmail.com> #332Jun 10, 2021 07:22PM

[Deleted User] <[Deleted User]> #333Jun 25, 2021 07:57PM

Comment has been deleted.

Message last modified on Jun 25, 2021 07:58PM

pr...@gmail.com <pr...@gmail.com> #334Jun 27, 2021 11:41AM

ni...@quantiphi.com <ni...@quantiphi.com> #335Jun 29, 2021 02:12PM

he...@gmail.com <he...@gmail.com> #336Jul 5, 2021 06:50AM

ra...@gmail.com <ra...@gmail.com> #337Jul 13, 2021 09:36AM

+1 me too.

[Deleted User] <[Deleted User]> #338Jul 20, 2021 09:20AM

+1 mee to

[Deleted User] <[Deleted User]> #339Jul 21, 2021 06:19PM

plz

pe...@gmail.com <pe...@gmail.com> #340Aug 3, 2021 02:07PM

th...@poppy.be <th...@poppy.be> #341Aug 5, 2021 10:34AM

We absolutely need timescaledb

ki...@gmail.com <ki...@gmail.com> #342Aug 6, 2021 06:53PM

is this ever going to be available?

Message last modified on Aug 6, 2021 06:54PM

go...@gmail.com <go...@gmail.com> #343Aug 12, 2021 09:57AM

We need it bad

mi...@google.com <mi...@google.com> #344Aug 24, 2021 11:05PM

Dear customers,

From this point, please star this Issue Tracker by clicking on the star icon on the left side of the ticket number if you are interested on the implementation of this feature.

Message last modified on Aug 31, 2021 10:56PM

mi...@google.com <mi...@google.com> #345Aug 31, 2021 11:03PM

This feature request is still on our engineering team's backlog and future updates will be posted on this ticket, but please note that it is not possible to provide an ETA for the implementation of this feature until it is approved.

va...@google.com <va...@google.com> May 30, 2024 07:16AM

Reassigned to va...@google.com.

va...@google.com <va...@google.com> Jun 11, 2024 09:12AM

Reassigned to gc...@google.com.

ms...@google.com <ms...@google.com> #346Aug 15, 2024 09:16AM

My customer Telefonica would also like to have support for timescaleDB

eb...@google.com <eb...@google.com> #347Aug 28, 2024 06:20PM

My cx,Planet Labs is interested in this feature.

Their use case: To monitor and measure a time series of customer and application behaviors. They are specifically interested in the time-based aggregates provided by timescaledb.

so...@google.com <so...@google.com> #348Sep 10, 2024 05:26PM

My cx, Plextrac is interested in this feature so they can migrate their database to Google Cloud.

Issue 64602105

Description

Issue summary

Comments

na...@google.com <na...@google.com> #2Aug 11, 2017 07:30PM

pa...@gmail.com <pa...@gmail.com> #3Nov 2, 2017 10:31AM

gr...@fiskekroken.org <gr...@fiskekroken.org> #4Nov 10, 2017 08:08AM

ha...@oden.io <ha...@oden.io> #5Nov 15, 2017 11:54PM

wi...@gmail.com <wi...@gmail.com> #6Nov 19, 2017 10:51AM

lo...@gmail.com <lo...@gmail.com> #7Nov 26, 2017 09:18PM

ca...@gmail.com <ca...@gmail.com> #8Nov 27, 2017 03:27PM

mt...@gmail.com <mt...@gmail.com> #9Dec 21, 2017 07:23PM

[Deleted User] <[Deleted User]> #10Jan 2, 2018 11:51PM

[Deleted User] <[Deleted User]> #11Jan 23, 2018 01:22PM

[Deleted User] <[Deleted User]> #12Jan 24, 2018 11:05AM

dp...@brightgate.com <dp...@brightgate.com> #13Jan 24, 2018 07:51PM

[Deleted User] <[Deleted User]> #14Jan 25, 2018 11:43PM

je...@gmail.com <je...@gmail.com> #15Jan 27, 2018 01:03AM

ch...@contentthread.com <ch...@contentthread.com> #16Jan 27, 2018 01:30PM

[Deleted User] <[Deleted User]> #17Jan 30, 2018 03:11AM

mi...@gmail.com <mi...@gmail.com> #18Jan 30, 2018 10:40PM

my...@gmail.com <my...@gmail.com> #19Feb 7, 2018 07:17PM

ne...@gmail.com <ne...@gmail.com> #20Feb 12, 2018 12:22AM

ba...@bad.so <ba...@bad.so> #21Feb 17, 2018 03:32PM

br...@gmail.com <br...@gmail.com> #22Feb 21, 2018 11:28AM

da...@diit.ca <da...@diit.ca> #23Feb 22, 2018 05:33PM

rn...@gmail.com <rn...@gmail.com> #24Mar 3, 2018 01:37AM

sk...@gmail.com <sk...@gmail.com> #25Mar 4, 2018 02:25AM

ba...@bad.so <ba...@bad.so> #26Mar 5, 2018 04:19AM

jo...@midnightlinux.com <jo...@midnightlinux.com> #27Mar 5, 2018 04:59AM

an...@mirusresearch.com <an...@mirusresearch.com> #28Mar 8, 2018 02:31PM

[Deleted User] <[Deleted User]> #29Mar 14, 2018 11:36AM

sr...@gmail.com <sr...@gmail.com> #30Mar 15, 2018 10:19AM

nf...@gmail.com <nf...@gmail.com> #31Mar 15, 2018 01:30PM

un...@gmail.com <un...@gmail.com> #32Mar 20, 2018 08:49PM

cw...@gmail.com <cw...@gmail.com> #33Mar 22, 2018 04:07PM

ja...@jargonia.co.uk <ja...@jargonia.co.uk> #34Mar 22, 2018 04:07PM

al...@mirusresearch.com <al...@mirusresearch.com> #35Mar 23, 2018 02:41AM

ga...@gmail.com <ga...@gmail.com> #36Mar 23, 2018 10:09AM

a....@convotis.com <a....@convotis.com> #37Mar 23, 2018 11:22AM

ac...@nes.ru <ac...@nes.ru> #38Mar 25, 2018 12:33AM

ar...@gmail.com <ar...@gmail.com> #39Mar 31, 2018 09:45AM

as...@gmail.com <as...@gmail.com> #40Apr 1, 2018 02:20AM

[Deleted User] <[Deleted User]> #41Apr 4, 2018 09:54AM

[Deleted User] <[Deleted User]> #42Apr 4, 2018 11:34AM

[Deleted User] <[Deleted User]> #43Apr 11, 2018 11:54AM

b....@gmail.com <b....@gmail.com> #44Apr 14, 2018 12:15PM

ab...@amperon.co <ab...@amperon.co> #45Apr 16, 2018 02:37AM

aj...@google.com <aj...@google.com> #46Apr 17, 2018 05:58PM

da...@we-riot.com <da...@we-riot.com> #47Apr 18, 2018 09:41PM

jm...@gmail.com <jm...@gmail.com> #48Apr 19, 2018 08:30PM

ko...@gmail.com <ko...@gmail.com> #49Apr 19, 2018 11:51PM

os...@aiven.io <os...@aiven.io> #50Apr 20, 2018 10:55AM

[Deleted User] <[Deleted User]> #51Apr 23, 2018 07:00PM

to...@nytimes.com <to...@nytimes.com> #52Apr 24, 2018 05:25PM

la...@fluxon.com <la...@fluxon.com> #53Apr 26, 2018 05:00PM

wi...@gmail.com <wi...@gmail.com> #54Apr 29, 2018 02:42PM

hu...@gmail.com <hu...@gmail.com> #55May 3, 2018 03:45AM

ma...@forestrock.co.uk <ma...@forestrock.co.uk> #56May 3, 2018 11:43AM

po...@gmail.com <po...@gmail.com> #57May 6, 2018 12:09PM

cl...@zen.ly <cl...@zen.ly> #58May 9, 2018 09:51AM

cs...@gmail.com <cs...@gmail.com> #59May 9, 2018 10:22AM

[Deleted User] <[Deleted User]> #60May 9, 2018 11:49AM

sr...@gmail.com <sr...@gmail.com> #61May 9, 2018 08:21PM

tw...@gmail.com <tw...@gmail.com> #62May 14, 2018 06:01PM

[Deleted User] <[Deleted User]> #63May 21, 2018 07:25PM

jo...@gmail.com <jo...@gmail.com> #64May 22, 2018 06:12PM

co...@gmail.com <co...@gmail.com> #65May 24, 2018 08:30AM

hr...@gmail.com <hr...@gmail.com> #66May 26, 2018 07:42AM

ma...@gmail.com <ma...@gmail.com> #67Jun 2, 2018 10:52AM

ra...@trueanthem.com <ra...@trueanthem.com> #68Jun 3, 2018 02:47PM

ja...@expeditors.com <ja...@expeditors.com> #69Jun 4, 2018 02:22PM

gu...@magic-carpet.ch <gu...@magic-carpet.ch> #70Jun 6, 2018 07:41AM

As...@ashtonkinslow.com <As...@ashtonkinslow.com> #71Jun 10, 2018 07:25AM

dy...@gmail.com <dy...@gmail.com> #72Jun 12, 2018 04:51AM

[Deleted User] <[Deleted User]> #73Jun 12, 2018 08:29AM

[Deleted User] <[Deleted User]> #74Jun 12, 2018 10:18AM

[Deleted User] <[Deleted User]> #75Jun 13, 2018 01:27PM

sh...@gmail.com <sh...@gmail.com> #76Jun 14, 2018 06:23AM

to...@gmail.com <to...@gmail.com> #77Jun 15, 2018 02:28PM