4 ms·
Creating views and triggers on the fly does sound like insanity. There's got to be a better way.
by buckbova 12y ago
Creating views and triggers on the fly does sound like insanity. There's got to be a better way.
- 15155 12y agoCreate triggers, fire all events off to a proper message broker for fanout. Events can be triggered directly in PG using an extension for AMQP or something, or in a standalone service, using whatever you can dream up.
- nunwuo 12y agoThere is: logical decoding http://www.postgresql.org/docs/9.4/static/logicaldecoding.html http://www.postgresql.org/docs/9.4/static/logicaldecoding.ht... I wonder why the author chose to waste time on this instead of doing things the proper way.
- ivarv 12y agoI'd guess ignorance? I'd never heard of 'logical decoding' before and the name of the feature doesn't lend itself to easy understanding. That said, thanks for pointing this out - it looks like yet another very useful PG feature!
- hammerandtongs 12y agoAt times it feels as if the entire Nosql industry was created by people not reading the Postgresql manual. edit: thanks for the link to logical decoding, looks very useful.
- justinsb 12y agoLogical decoding was only recently added in Postgres (9.4)? I'm not sure on the privileges required for logical decoding in postgres, but typically it requires 'root' access because it lets you see all the data in the system. So triggers can often be used on a shared database, where you might not be allowed to access the transaction log.
- numtel 12y agoSee this issue: https://github.com/numtel/pg-live-select/issues/1 https://github.com/numtel/pg-live-select/issues/1 I would love to see a pull request for the "proper way." Thank you for your help.