3 ms·
I certainly wasn't saying the feature should not exist because it's hard.... merely, do it right or not at all. The culture on the Postgres development side ha
by chrisfarms 13y ago
I certainly wasn't saying the feature should not exist because it's hard.... merely, do it right or not at all.
The culture on the Postgres development side has always taken a very conservative approach, which carries with it much trust that the features that exist work very well.
Introducing a half-baked feature would break this trust. And so I would rather wait.
- spacemanmatt 13y ago+1 When you have a huge investment in your data, a conservative approach to database servers is full of merit. Once I began to understand concurrent design my years of MySQL experience were suddenly curdled. I had to switch to a server/community that care about integrity, and do not play fast and loose with new features. It's not a popularity contest.
- nuclear_eclipse 13y agoI would rather see a single, well-defined and correct implementation, even if it's really slow, than to not have it at all...