3 ms·
Another example of how impressive Postgres is, well done. I’m always amazed by how much faster Postgres gets with each release - unlike most other softwares tha
by garyclarke27 8y ago
Another example of how impressive Postgres is, well done.
I’m always amazed by how much faster Postgres gets with each release - unlike most other softwares that often get slower.
Many parallel processing improvements in 11 should keep this up. Array and Composite Domains, Stored Procedures, Awesome Window functions even better framing / exlusion.
Very few weakness vs Oracle now, apart from one glaring weakness - Materialized views - lack of auto incremental refresh, severely limits their usefulness. (SQL Server Mat views also fairly useless beacuse they have so many limitations).
Would love to see - NOT IN Foreign key constraint - I would imagine this would be quite easy to implement on the back of existing IS In Foreign Keys, would be incredibly useful.
Also why not increase the default identifier length from 63 to 127? I know can be done on first install(only then) so is a pain to do, I find long constraint names useful for understanding errors.
- iKevinShah 8y agoWhat I feel lacking in PG(though it can be easily managed by adding respective plugins) is the lack of unsigned int alike (from MySQL) AND UNIQUE columns be case-insensitive or an option of having case-insensitive unique columns while default be case-sensitive (As it is currently)
- bmdavi3 8y agoThere's no 'CASE INSENSITIVE' option for unique indexes, but you can unique on lower(my_column) to achieve the safe effect.
- iKevinShah 8y agoyes that is what I do currently as a workaround. I wished we had an option for case-insensitive unique indexes though..
- deleted 8y ago[deleted]
- Deimorz 8y agoYou can do case-insensitive columns by enabling the "citext" module, which is included but not enabled by default: https://www.postgresql.org/docs/current/static/citext.html https://www.postgresql.org/docs/current/static/citext.html