> I would just like to enable hCaptcha when registering new users, but there's no way to configure this with Supabase.
this is possible, the docs are here: https://supabase.com/docs/guides/auth/auth-captcha
6,216 karma · joined April 6, 2017
copple [at] supabase [dot] io
this is possible, the docs are here: https://supabase.com/docs/guides/auth/auth-captcha
there are some other interesting extensions in this space - onesparse[0] is early in development but pretty exciting as it builds on SuiteSparse which is very mature
I can see this would be useful in multi-tenant applications
The number 1 feature of your project should be security. Supabase is just Postgres + tools - it will be as secure as you decide to make it.
supabase team here. Yes, we offer an auto-generated API (using PostgREST). But users can also connect directly to their Postgres database or through a connection pooler. People have preferences, so we offer options.
nice work OP - i like this version of tech where we all get along. the project looks great, good luck!
This is a Postgres-native Queue. It's built with the PGMQ extension[0] which the Tembo team have generously licensed their extension with the OSI-compatible PostgreSQL license. PGMQ has API parity with AWS SQS and RSMQ.
Our implementation is compatible with the rest of the supabase stack. With RLS enabled, you can use the client libs to CRUD messages/tasks. eg:
import { createClient } from '@supabase/supabase-js'
const queues = createClient(url, key, {
db: { schema: 'pgmq_public' },
})
const { data, error } = await queues.rpc('send', {
queue_name: 'foo',
message: { hello: 'world' },
})
[0] PGMQ: https://github.com/tembo-io/pgmq
i didn't try it locally yet but it looks like the cloud version can create SQLite databases inside the browser? Assuming the open source version does too, can you also "connect" to those databases somehow?
EDB and Cybertech definitely made a great start with Zheap[0] although the initiative stalled for whatever reason
Hopefully the community can support this effort to improve the Table AM API - it would be beneficial even beyond oriole. As you point out, a Pluggable Storage system in Postgres would open up a few new use cases
For those jumping to the comments wondering if it's worth watching: TigerBeetle[0] is a database for managing financial transactions. They extend the testing practices of FoundationDB (now spun out into Antithesis[1]), going a layer deeper to test for data integrity when there is disk io corruption (~20:30)
In the demo, they have created a game-like simulation that runs in the browser. You can watch Joran "attack" database nodes and simulate corruption. The entire presentation is impressive and the simulator is very entertaining.
while i'd generally agree with this, in the case of TigerBeetle i think it's safe to trust their tech based on their test-suite/practices - one of the most impressive things I've seen in the past 5 years.
they extend the testing practices of FoundationDB (now spun out into Antithesis[0]), going a layer deeper to test for data integrity when there is disk io corruption. check out from ~20:30 in this demo:
i use f5bot[0] and have notifications set up for "supabase". it helps that supabase is a unique word so I don't get many false-positives.
Oriole has joined us at supabase now and it’s being worked on full time by Alexander and his team. Here is the patch set:
https://www.orioledb.com/docs#patch-set
It will be available to try on the supabase platform later this year too
One request for the "todos" at the end would be a small docker container with onesparse pre-installed - it would help a lot for getting started
Also I may have missed this, but are there more docs yet, or just the readme for now?
- If the foreign server is close (latency) that’s great
- if your query is complex then it helps if the postgres planner can “push down” to mssql. That will usually happen if you aren’t doing joins to local data
I personally like to set up the foreign tables, then materialize the data into a local postgres table using pg_cron. It’s like a basic ETL pipeline completely built into postgres
Massive improvements to vacuum operations:
"PostgreSQL 17 introduces a new internal memory structure for vacuum that consumes up to 20x less memory."
"pg_basebackup, the backup utility included in PostgreSQL, now supports incremental backups and adds the pg_combinebackup utility to reconstruct a full backup"
"The PostgreSQL foreign data wrapper (postgres_fdw), used to execute queries on remote PostgreSQL instances, can now push EXISTS and IN subqueries to the remote server for more efficient processing."Supabase is designed to work like LEGO, you add the blocks you want, and we keep everything as modular as possible so that you can combine it with other services like kratos if you prefer
our postgres offering costs roughly equivalent of RDS so if you use it with Django I don’t think you will come close to 20-40x a VPS, ymmv, depending on your workload
We have an Auth service, but since you use Django you wouldn’t need it - sounds like you’d only need postgres (like a lot of our customers)
https://supabase.com/docs/guides/database/extensions/pgroong...
Usually FDWs need to be "pre-installed" on Postgres which makes it harder for Postgres platforms to support a wide variety of FDWs. With WebAssembly, the FDW's can safely be installed from S3 or GitHub.
There are some trade-offs: the performance isn't as good as a "native" FDW. That said, we think the flexibility makes it worthwhile, and we'll improve the performance over time.
Background: what is a FDW? Foreign Data Wrappers are a core feature of Postgres that allow you to access and query data stored in external data sources as if they were native Postgres tables. For example, the Stripe FDW allows you to query all your customers from Stripe inside your postgres database:
select
customer_id,
name
from
stripe.customers;
[1] paddle: https://fdw.dev/catalog/paddle/