PostgreSQL used fsync incorrectly for 20 years

Re:PostgreSQL used fsync incorrectly for 20 years by ams6110 on Sunday February 10, 2019 @08:00PM (#19131297)

Not the worst thing in the world. I have trouble reading code with very long identifiers. Conventionally, a line of code should not exceed 80 characters or so. That's pretty hard if identifers are 60+ characters by themselves. If your project has standard abbreviations for things, "63 characters ought to be enough for anybody"

[ Parent | on HN ]

Re:PostgreSQL used fsync incorrectly for 20 years by majewsky on Monday February 11, 2019 @02:22AM (#19132628)

I had a project last year where DB names were autogenerated per tenant, with the tenant ID being a UUID, so you're left with 63-36=27 characters. Starts to feel narrow.

(Putting tenant_id as a column was not an option because for each tenant, a third-party software was started that wanted to have its own DB.)

[ Parent | on HN ]