Postgres 9.5 Release Notes
postgresql.org
Postgres 9.5 Release Notes
1–10 of 11 posts
Re: Postgres 9.5 Release Notes
#2Re: Postgres 9.5 Release Notes
#3In old-school systems you normally have one database user and a connection pool set up in the app with that user. Row level access is handeld with join tables to sort out what data is accessible for the specific users (sent as parameter to most queries).
With row-level security you would crate a db-user for each application user and also its own connection pool?
Re: Postgres 9.5 Release Notes
#4Re: Postgres 9.5 Release Notes
#5Re: Postgres 9.5 Release Notes
#6Anyone have ever built an application utilising row level security? In old-school systems you normally have one database user and a connection pool set up in the app with that user. Row level access is handeld with join tables to sort out what data is accessible for the specific users (sent as parameter to most queries). With row-level security you would crate a db-user for each application user and also its own conn…
Re: Postgres 9.5 Release Notes
#7Dupe: http://www.postgresql.org/about/news/1636/
Re: Postgres 9.5 Release Notes
#8Dupe: http://www.postgresql.org/about/news/1636/
This post links to the release notes. The post you mention links to the press release. They contain similar but different information.
Re: Postgres 9.5 Release Notes
#9Earlier quoted context omitted.
This post links to the release notes. The post you mention links to the press release. They contain similar but different information.
Sure, but this is about the new release — I don't see the point of having two threads about the same thing. (The press release links to the release notes, too.)
Personally, I always read the release notes but am less interested in the press release. I think many others prefer the opposite, hence my posting both. You raise a valid point though.
Re: Postgres 9.5 Release Notes
#10Anyone have ever built an application utilising row level security? In old-school systems you normally have one database user and a connection pool set up in the app with that user. Row level access is handeld with join tables to sort out what data is accessible for the specific users (sent as parameter to most queries). With row-level security you would crate a db-user for each application user and also its own conn…
This allows pooling.
I made a quick app with pg 9.5 rc1, rls, spring data rest which I'm hoping to share next week.