3 ms·
That's not exactly true. You can write your own patch for a feature and there's a good chance they'll decide they don't want it. It's their prerogative, but als
by DangitBobby 4y ago
That's not exactly true. You can write your own patch for a feature and there's a good chance they'll decide they don't want it. It's their prerogative, but also slightly upsetting when you know they're blocking features you want. Just observe the bike shedding over a trailing commas patch [1].
1. https://postgrespro.com/list/thread-id/1853280 https://postgrespro.com/list/thread-id/1853280
- TheP1000 4y agoThere are lots of good reasons in that thread why the patch was declined. The patch made things more lenient which makes things less compatible (this whole thread is about ANSI SQL standards and they do matter) and changes what was an error behavior to now silently succeed. +1 to postgres devs for curating patches.
- DangitBobby 4y agoI read the thread and have to disagree with "lots of good reasons". I'm pretty sure there are plenty of things in the postgres dialect that are not cross compatible with any other dialect. I agree with curating patches in general, but it's a double edged sword and inaccurate to say you can just spend your weekend to get something you care about.