| From: | Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com> |
|---|---|
| To: | Achilleas Mantzios - cloud <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Fwd: A million users |
| Date: | 2024-11-13 11:30:26 |
| Message-ID: | CAM+6J97dYumtR2P+J6OdiLcAUqKGV0K3Nm3n=gZ5z+PMwYYhAg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Nov 13, 2024, 4:42 PM Achilleas Mantzios - cloud <
a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> wrote:
>
> 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 | Date | Subject | |
|---|---|---|---|
| Next Message | Vijaykumar Jain | 2024-11-13 11:40:26 | Re: Fwd: A million users |
| Previous Message | Achilleas Mantzios - cloud | 2024-11-13 11:12:24 | Re: Fwd: A million users |