PostgreSQL database restrictions in commercial application [closed]

Licensing Restrictions:

None, the code is open.

Maximum size for a database:

unlimited (32 TB databases exist)

Maximum size for a table:

32 TB

Maximum size of a line:

1.6 TB

Maximum size for a field:

1 GB

Maximum number of rows in a table:

unlimited

Maximum number of columns in a table:

250-1600, depending on column types

Maximum number of indexes in a table:

unlimited

Maximum number of connections:

By default, 100 concurrent connections, but can be configured in postgresql.conf

Source: link

Licensing is quiet and you can do anything.

There are no major restrictions, and it can run well. Or not. Because usually what makes the most difference is the person knowing what he is doing, this is much more difficult. For most applications choosing something that is not ideal is a minor problem. Also because in general the wrong choice is made due to general ignorance and this will cause a much bigger problem.

Studying the basics to be able to evaluate all points is something much more important than knowing some specific information. What is the use of knowing who discovered Brazil, if this information may be false, incomplete or confusing, or irrelevant, or not knowing why you need to know this?

There are no limitations of connections in the software except by configuration. Of course there is a practical limit, but it depends on a number of factors. And this does not matter much, because in corporate applications does not even come close and in web applications will only come if everything was wrongly architected.

The maximum data size is theoretical and should not worry, because even if one makes an application that needs so much will be a professional who dominates the subject a lot. There are specific limitations that in almost everything is theoretical, again because if surpassing is doing something wrong. Everything has a solution. The most important limit is the number of columns in a table that is 250 in some cases, in practice the limit may be 1600 depending on the types used, and if you need more than 250 you have a great chance of doing something wrong, and you have to work around . Another is the limit of 1GB per column, which is quiet for almost everything.

You have a answer in the OS that still keeps the limits described .

There is no network connection limit with other machines, only non-client-server databases have a limitation on this. Obviously there is a practical limit

The decision of which database to use and adopted model goes through other things. It is not because you know this that you will make the right decision on which database to use.

I would talk forever to look at the documentation to see these things, this is the most important to know what to do, but in this specific case have taken, which shows that the product started getting more marketeiro and this is a bad sign, this is a project that prized much for engineering.