Hello guys!
I've faced an interesting case with cascade drops. If we drop some view
that is dependency for another view then drop cascade will not check
permissions for cascade-droppping views.
Short example is:
create user alice with password 'apassword';
create user bob with password 'bpassword'
On 2022-04-05 19:25:24 -0400, Mladen Gogala wrote:
> NULL is strange. Relational databases use ternary, not binary logic.
> In the woke vernacular, one could say that Postgres is non-binary.
> NULL literally means "no value".
I prefer to think of NULL as "unknown value". That way the ternary logic
On 4/4/22 09:21, J. Roeleveld wrote:
This was actually the case, I forgot there is 1 NULL-value in that list.
Personally, I think NULL should be treated as a seperate value and not lead to
strange behaviour.
NULL is strange. Relational databases use ternary, not binary logic. In
the woke verna
Sorry for the confusion I caused. The question about connection management
and pg bouncer was a distraction and should have been addressed separately.
When having a mixture of OLTP and OLAP on the same primary databases, is
there any benefit to declaring long running report type connections
as SER
