News for hackers. Stuff that matters.
Re:Surviving Without a Superuser in Postgres 16 by idorosen on Thursday January 26, 2023 @03:12AM (#34529062)
Finally.
[dead]
Re:Surviving Without a Superuser in Postgres 16 by tstrimple on Thursday January 26, 2023 @03:49PM (#34538617)
I think ChatGPT may have escaped.
Re:Surviving Without a Superuser in Postgres 16 by tarotuser on Thursday January 26, 2023 @05:36PM (#34539883)
My apologies. I misunderstood the nature of said question.

After surveying my field of information, I believe that Oracle databases are far superior to anything else on the market.

/Cringe

Re:Surviving Without a Superuser in Postgres 16 by Karellen on Thursday January 26, 2023 @06:35PM (#34540397)
If OracleDB is fast and web scale I will use it. Is it web scale?

Does OracleDB support sharding? Shards are the secret ingredient in the web scale sauce. They just work.

Re:Surviving Without a Superuser in Postgres 16 by nickpeterson on Thursday January 26, 2023 @09:20PM (#34541689)
What about impotence mismatch?
Re:Surviving Without a Superuser in Postgres 16 by jph on Thursday January 26, 2023 @01:45PM (#34536600)
Thank you so much for working on the role security-- it's a major pain point with Postgres, such as for teams of teams that each need to create their own databases yet should be isolated from interfering with other teams' databases.

And I will gladly donate money to help toward a new feature that can scope by role name, such as a role "foo" that can create/delete/manage databases that start with foo_, such as foo_dev, foo_test, foo_prod, etc.

Re:Surviving Without a Superuser in Postgres 16 by chungy on Thursday January 26, 2023 @02:14PM (#34537137)
> it's a major pain point with Postgres, such as for teams of teams that each need to create their own databases yet should be isolated from interfering with other teams' databases.

I'm curious: Why not set up multiple clusters for this?

Re:Surviving Without a Superuser in Postgres 16 by evol262 on Thursday January 26, 2023 @03:07PM (#34537986)
Because sometimes you have multiple, discrete applications which should be isolated, but need high performance (40gbe, optane, huge amount of CPU concurrency, whatever) and don't want to slice up the server for virtualization or run it in the cloud. Or you won't want to manage multiple pgpool/pgbouncer configs. Or you want BGP-based site failover and it's more complex with more clusters, or replicating massive data warehouses/ML data/preprod is substantially faster if it can be a job on the same server instead of replication, or...
Re:Surviving Without a Superuser in Postgres 16 by jchw on Thursday January 26, 2023 @03:14PM (#34538082)
I wonder if something like Neon can help here. The pitch is that it refactors the dataplane out so that you can scale individual databases from 0. If it's suitable for scaling multitenant workloads, then it should be sufficient for multiple teams, I assume?

That said, it's a fork of Postgres, and I bet there's plenty of limitations. But I still find it interesting nonetheless.

Re:Surviving Without a Superuser in Postgres 16 by chungy on Thursday January 26, 2023 @04:22PM (#34539025)
If we're talking production, it's still trivially easy to have multiple clusters on the same OS without resorting to virtualization or cloud.

As the original post sounded though, it struck me more as a development thing (because why would production allow such access at all?)

Re:Surviving Without a Superuser in Postgres 16 by Someone on Thursday January 26, 2023 @04:14PM (#34538946)
Can’t you do effectively the same with schemas? Something like

  create schema foo;
  grant all on all tables in schema foo to foo;
would allow role “foo” to “create/delete/manage databases in schema foo, such as foo.foo_dev, foo.foo_test, foo.foo_prod, etc.

Or do you want a second level (possibly a hierarchy) of schemas?

Re:Surviving Without a Superuser in Postgres 16 by chungy on Thursday January 26, 2023 @04:23PM (#34539034)
Schemas are underneath databases, but same idea :)
Re:Surviving Without a Superuser in Postgres 16 by Shorn on Thursday January 26, 2023 @10:45PM (#34542199)
Hopefully this will help finally smooth off the rough edges when trying to deal with Postgres in both RDS (for test/prod) and locally (for dev).

It's awkward to have logic branches in the database migrations to deal with the differences between the two environments.