Comment by simonw

4 days ago

They /tmp file mechanism sounds like a bit of a hack, is that definitely necessary?

It may be possible to create a SQLite in-memory database instead and then load the binary blob data into it using the backup API or some kind of trick with VACUUM INTO.

4 comments

simonw

michelpp 4 days ago

I think the right approach would be to store the sqlite database as a varlena type that can be TOASTed and then "expanded" using the Expanded Datum API so that it's a live open database connection for the life of the transaction:

https://www.postgresql.org/docs/17/xtypes.html#XTYPES-TOAST

https://github.com/postgres/postgres/blob/master/src/include...

frectonz 4 days ago
Thanks i will look into this more, /tmp stuff is most definitely a hack.
- michelpp 4 days ago
  
  Here's an example of a simple expanded object to start from:
  https://github.com/michelp/pgexpanded