Status Update
Comments
gh...@google.com <gh...@google.com>
gh...@google.com <gh...@google.com> #2
Hello,
Thanks for the feature request! This has been forwarded to the Cloud SQL Team so that they may evaluate it. Note that there are no ETAs of implementation for feature requests. All communication regarding this feature request is to be done here.
da...@gmail.com <da...@gmail.com> #3
di...@gmail.com <di...@gmail.com> #4
br...@stayhvn.com <br...@stayhvn.com> #5
Cloud SQL supporting pgvector would go a long way towards making Google the standard-bearer here.
ke...@gmail.com <ke...@gmail.com> #6
ra...@gmail.com <ra...@gmail.com> #7
ma...@wildwalks.com <ma...@wildwalks.com> #8
di...@gmail.com <di...@gmail.com> #9
It's a deal breaker for choosing Cloud SQL for new projects as well as a reason to migrate for existing ones.
yu...@cohere.io <yu...@cohere.io> #10
ed...@emansolutions.com <ed...@emansolutions.com> #11
se...@round.tech <se...@round.tech> #12
ja...@gmail.com <ja...@gmail.com> #13
va...@google.com <va...@google.com>
ku...@google.com <ku...@google.com> #14
Hello,
To expedite the process, I have reported this issue to the Cloud SQL Engineering team once again. However, please note that there is no ETA or guarantee of implementation for this at the present moment. Rest assured, we’ll keep you updated on every update we receive from the team. Any further updates on this issue will be communicated here.
dy...@gmail.com <dy...@gmail.com> #15
db...@spotify.com <db...@spotify.com> #16
wh...@gmail.com <wh...@gmail.com> #17
[Deleted User] <[Deleted User]> #18
jo...@packetfabric.com <jo...@packetfabric.com> #19
cr...@gmail.com <cr...@gmail.com> #20
INSERT INTO items (embedding) VALUES ('[1,2,3]'), ('[4,5,6]');
I need this in my life!
ra...@linear.app <ra...@linear.app> #21
hu...@amberbit.com <hu...@amberbit.com> #22
[Deleted User] <[Deleted User]> #23
di...@gmail.com <di...@gmail.com> #24
jo...@gitlab.com <jo...@gitlab.com> #25
ar...@gitlab.com <ar...@gitlab.com> #26
em...@gmail.com <em...@gmail.com> #27
+1 With the advent of vector databases the need for this extension in cloud sql is becoming even more relevant. Please add as it would allow us to build better products on top of cloud sql. Thanks!
fi...@addonsforgapps.com <fi...@addonsforgapps.com> #28
+1, would love to see support in Cloud SQL
be...@gmail.com <be...@gmail.com> #29
te...@gofynd.com <te...@gofynd.com> #30
as...@gwi.com <as...@gwi.com> #31
st...@trustlayer.io <st...@trustlayer.io> #32
vi...@trustlayer.io <vi...@trustlayer.io> #33
ku...@google.com <ku...@google.com> #34
Hi,
Please note that this issue is a duplicate of
In case you want to report a new issue, please do not hesitate to create a new
da...@gmail.com <da...@gmail.com> #35
io...@gmail.com <io...@gmail.com> #36
ha...@gmail.com <ha...@gmail.com> #37
Since this issue has the most activity, and shows the community's interest in this feature, could we reverse which one is the duplicate, and re-open this one and mark the other as the duplicate? I really want this feature and would love to ensure the powers that be can prioritize based on community interest!
wy...@gmail.com <wy...@gmail.com> #38
cd...@gmail.com <cd...@gmail.com> #39
ga...@tibas.media <ga...@tibas.media> #40
sn...@gmail.com <sn...@gmail.com> #41
ea...@gmail.com <ea...@gmail.com> #42
to...@gmail.com <to...@gmail.com> #43
hi...@gmail.com <hi...@gmail.com> #44
mj...@gmail.com <mj...@gmail.com> #47
dk...@gmail.com <dk...@gmail.com> #48
ka...@gmail.com <ka...@gmail.com> #49
em...@vml.com <em...@vml.com> #50
ge...@vml.com <ge...@vml.com> #51
lu...@adminremix.com <lu...@adminremix.com> #52
st...@uman.ai <st...@uman.ai> #53
+1
Description