(www.crunchydata.com)

157 points craigkerstiens | 5 comments | 17 Oct 24 16:18 UTC | HN request time: 0.667s | source

1. whalesalad ◴[17 Oct 24 21:26 UTC] No.41873978[source]▶

I wish RDS made it easy to add custom extensions like this.

2. wdb ◴[17 Oct 24 22:56 UTC] No.41874650[source]▶

or Google Cloud

3. treefarmer ◴[18 Oct 24 00:41 UTC] No.41875299[source]▶

Yeah, I'm still surprised they haven't added a list of unsupported extensions (that you can add but they're not responsible for the performance of).

replies(1): >>41885515 #

4. bastawhiz ◴[19 Oct 24 03:49 UTC] No.41885515[source]▶

Amazingly their own aws_s3 extension isn't even supported in their multi-az cluster configuration.

5. mdaniel ◴[22 Oct 24 20:15 UTC] No.41918212[source]▶

I was expecting https://github.com/wasmerio/wasmer-postgres#usage--documenta... to catch on, and some how must have gotten it mixed up with Trusted Language Extensions <https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Postg...> (and https://github.com/aws/pg_tle/tree/v1.4.0#getting-started ) but unless someone decides to implement every single bit of a modern PG extension in JS (or Perl), that's just some hello-world nonsense

Pg_parquet: An extension to connect Postgres and parquet