1) Analyze “performance”, can you have ~50 DB users instead of re-implementing a custom system?
2) (Solved) How does the user check (what is a SQL statement) what permissions he has in the table?
Solution:
SELECT HAS_TABLE_PRIVILEGE('user','table','insert')
I would rather not reimplement System, because a good security system is not easy to implement.
Our system will run on the local network, where no more than 50 clients connect to The same local server. We are creating a DB user for each client to take advantage of the postgresql permission system.
1) Analyze “performance”, you can have ~50 DB users instead of reimplementing Custom system?
2) (Solved) How does the user check (what is a SQL statement) what permissions he has in the table?
Solution:
SELECT HAS_TABLE_PRIVILEGE('user','table','insert')
I would rather not reimplement System, because a good security system is not easy to implement.
To answer the user/performance question: maybe not. The only real risk depends on how much The user has unique security permissions (for example, if each of these 50 users has different permissions for each table/schema in the database). In practice, this will never happen, as long as you have a sane permission Group system, you should be fine.