Huh ok, so that pegs the max size for a row at 1.6 TB then. How do you get
to unlimited when there is a max size per attribute and max # of
attributes. Also, I gather that 1599 is probably a safer max attr # than
1600 to make room for an extra attr during UPDATE (otherwise it would max
out during the query)
Now I just can't imagine what would go into a 1.6TB row but...
Joshua b. Jore ; http://www.greentechnologist.org
On Thu, 11 Jul 2002, Richard Huxton wrote:
> On Thursday 11 Jul 2002 9:24 am, huang@tanpopo-tane.com wrote:
> > How many tables can be created in one datebase?
> > How many fields can be created in one table?
> > thank you
>
> See http://www3.uk.postgresql.org/users-lounge/limitations.html
>
> Maximum size for a database = unlimited (60GB databases exist)
> Maximum size for a table = 64 TB on all operating systems
> Maximum size for a row = unlimited in 7.1 and later
> Maximum size for a field = 1GB in 7.1 and later
> Maximum number of rows in a table = unlimited
> Maximum number of columns in a table = 1600
> Maximum number of indexes on a table = unlimited
>
> I am not aware of any limit on the number of tables, I should think practical
> considerations regarding management would cause problems before you hit a
> real limit.
>
> - Richard Huxton
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>