Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1V1wyT-0002Uj-TW for pgsql-admin@arkaria.postgresql.org; Wed, 24 Jul 2013 11:11:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1V1wyT-0006jS-CR for pgsql-admin@arkaria.postgresql.org; Wed, 24 Jul 2013 11:11:17 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1V1wyS-0006jM-I2 for pgsql-admin@postgresql.org; Wed, 24 Jul 2013 11:11:16 +0000 Received: from mail-pa0-x230.google.com ([2607:f8b0:400e:c03::230]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1V1wyP-00009R-1w for pgsql-admin@postgresql.org; Wed, 24 Jul 2013 11:11:15 +0000 Received: by mail-pa0-f48.google.com with SMTP id kp1so527120pab.7 for ; Wed, 24 Jul 2013 04:11:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version:x-mailer; bh=NgySq1OPb2BfQeJ+nLEYjhTL6IJ0B7SPbVuplrwUxQE=; b=rPyxIObU2CPr1iNb5NGbPpMVjSPhuc5kPcVwY44IrjYaEGtzTdM3nhPEmXm3kHh7wP CaeVzZzC+MWXyScscWoDJ11Rcu4+uqF6LQUVsIfuqEQ5CAFfpxUS8O8nbuPIXKlubamJ l4/XunAZR1gmaHQcl+lwglL1QcQGyhR4C9JlBfddvmw5uEAvEOikLw7J251t6lkE6hW7 LWn3qERm6bCVxBw1sl9Vsvu8gg6c2B0teDg62Ar7sgF4dSL+Q/CF0Wow6RZvs73ZNO+0 oIr4eK6T5gC+5pzYY0HVq85nEzU0vpDUHlkkZxuOmpYZWcGBC3ZWP7QHTwOMrdTWxpgF pZZQ== X-Received: by 10.66.192.234 with SMTP id hj10mr42439261pac.183.1374664272223; Wed, 24 Jul 2013 04:11:12 -0700 (PDT) Received: from [192.168.1.34] ([122.164.69.110]) by mx.google.com with ESMTPSA id wf7sm50892823pac.20.2013.07.24.04.11.08 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 24 Jul 2013 04:11:10 -0700 (PDT) From: Anand Muthukrishnan Content-Type: multipart/alternative; boundary="Apple-Mail=_D18C3422-F742-4745-9090-2C74A2DFF423" Subject: Postgres schema having > 20,000 schemas Message-Id: Date: Wed, 24 Jul 2013 16:41:07 +0530 To: pgsql-admin@postgresql.org Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) X-Mailer: Apple Mail (2.1508) X-Pg-Spam-Score: 0.7 (/) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org --Apple-Mail=_D18C3422-F742-4745-9090-2C74A2DFF423 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Can a single Postgres database contain more than 20,000 schemas? What = are the implications of such a database design. I was reading about postgres schemas here - = http://www.postgresql.org/docs/8.2/static/ddl-schemas.html and I'm = planning to create one schema per account in my multi-tenant Ruby on = Rails app. Each schema would have a set of tables to store data of the = relevant account. Each user/schema for all the features we offer, could have 50-60 tables. Can postgres handle all of this without any hiccups, provided I allocate = a large EC2 instance to host the database server ? By experience if any one faced trouble with such number of schemas in = postgres, they could share and i thought i can get more guidance to = avoid such pitfalls. --Apple-Mail=_D18C3422-F742-4745-9090-2C74A2DFF423 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii = --Apple-Mail=_D18C3422-F742-4745-9090-2C74A2DFF423--