iemejia

@chatmasta Thanks again for the pointer. I just added the implementation now for the images based on PG 18+ I really like the idea of adding your layers at deploy time so this is a nice improvement.

Working on it. Great idea!

Good ideas, thanks. My target audience is both less technical and technical users who don't care about the low level details of databases but just want to run their code that uses the db extensions without the need to learn about the internals of the database to be able to use them.

Oh that's excellent. Thanks for sharing. I was not aware at all I cam going to take a look at it.

Yes, I thought this approach should work, but why nobody has done it. The only real issue is file collisions, which I test for aggressively. So far, I've only found a few minor cases that I either worked around or reported to the relevant projects (e.g. some projects package the extension with a generic README.md file) instead of an extension-specific one.

One surprising benefit that I hadn't considered when implementing this is that when I add new extensions or update existing ones, users only need to update the affected layers. As a result, update times are minimal.