fooododododo

10 ms·

1. 1.▲
   by fooododododo 2y ago

   Curious what your opinion on plpgsql functions is? Could easily solve your initial problem (if I follow). They don't seem to come up much though
2. 2.▲
   by fooododododo 2y ago

   Do they ever write plpgsql? If not why not?
3. 3.▲
   by fooododododo 2y ago

   Is everything in pgdump in the information schema?
4. 4.▲
   by fooododododo 2y ago

   Why not run Pg in a container if that's what's in prod?
5. 5.▲
   by fooododododo 3y ago

   Agree re trigger maintenance Re orm, I'm strongly biased towards only using them when they (1) are absolutely necessary or provide some extreme benefit (2) are able to output the raw SQL to be executed on the db (3) the SQL to be exe
6. 6.▲
   by fooododododo 3y ago

   Seems like a rant rather than a comment to the post? Timescale has continuous aggregates that might be interesting, writing a table built by a trigger isn't hard, and some might say having a separate connection pooler is a feature rath
7. 7.▲
   by fooododododo 3y ago

   Tracking triggers etc is pretty straightforward, just put them in a repo and apply them as part of a schema change. Testing them can be tricky, as unit tests aren't as likely to capture the locks/time that can be an issue when the