Re: Maximum number of sequences that can be created - Mailing list pgsql-performance

From Greg Spiegelberg
Subject Re: Maximum number of sequences that can be created
Date
Msg-id CAEtnbpWzxF6sLcqYL7QW+nntF5NtBsXW=4a4J8d1Sej6mxwitg@mail.gmail.com
Whole thread Raw
In response to Re: Maximum number of sequences that can be created  (Craig James <cjames@emolecules.com>)
Responses Re: Maximum number of sequences that can be created  (Craig James <cjames@emolecules.com>)
List pgsql-performance
On Sun, May 13, 2012 at 10:01 AM, Craig James <cjames@emolecules.com> wrote:

On Sun, May 13, 2012 at 1:12 AM, Віталій Тимчишин <tivv00@gmail.com> wrote:

The sequences AFAIK are accounted as relations. Large list of relations may slowdown different system utilities like vacuuming (or may not, depends on queries and indexes on pg_class).

Not "may slow down."  Change that to "will slow down and possibly corrupt" your system.

In my experience (PG 8.4.x), the system can handle in the neighborhood of 100,000 relations pretty well.  Somewhere over 1,000,000 relations, the system becomes unusable.  It's not that it stops working -- day-to-day operations such as querying your tables and running your applications continue to work.  But system operations that have to scan for table information seem to freeze (maybe they run out of memory, or are encountering an O(N^2) operation and simply cease to complete).

Glad I found this thread.

Is this 1M relation mark for the whole database cluster or just for a single database within the cluster?

Thanks,
-Greg
 

pgsql-performance by date:

Previous
From: Ondrej Ivanič
Date:
Subject: Re: pg_dump and thousands of schemas
Next
From: Tom Lane
Date:
Subject: Re: pg_dump and thousands of schemas