4 ms·

yes, I'm proposing stored procedure without the management headache

• manigandham 7y ago
  Ah, so temporary stored procedures that are created and cached at the connection level and lifetime. Makes sense, might be worth a feature request to the PG team.
  • janpot 7y ago
    Or longer, they can exist for the lifetime of a specific version of my app. they'd why I'd cache and identify by their hash.
    • manigandham 7y ago
      If you're doing that then why not just use stored procedures? Prefix with a version and dropping them to cleanup is a one liner. The only issue is dependency tracking in case you change any schemas but that's an issue with any saved code in the database.
    • munk-a 7y ago
      How are you going to identify them by hash or know which hash is significant? Why not store that determiner in the SP name and use that to pick and chose different versions based on that determiner. Unless each binary gets its own hash (in which case you could solve it by building the SP when the package is built and then injecting it into the binary) there's some piece of information you'd use to chose which one to use - why obfuscate that information behind a hash instead of just using it directly as a descriptor?