Exactly! In the later versions, security gets more and more refined and strengthened. So ppl should think about moving away from "public" , and start implementing finer grained schemes of security, as you suggest. + \dp shows prettier than having 1000+ users listed.
I wanted to just communicate the limits.
a lot of postgresql architecture can leverage the resources and scale, but not all.
i had 100s of 1000s of tables on my setup where i worked last.
if i did \dt it would freeze all the time. i had to exit the pdwl session, check the source code of how the partition was named and then look for what I wanted.
if things are pretty with psql or not should not be a criteria for how many objects you want to have.
i would expect clear exceptions so one knows what the real problem is.
the error I got did not in anyway communicate the role limits for col size limits.
From:
Alvaro Herrera Date: Subject:
Re: Fwd: Fwd: Postgres attach partition: AccessExclusive lock set on different tables depending on how attaching is performed
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
✖
By continuing to browse this website, you agree to the use of cookies. Go to Privacy Policy.