This talk is about the need of multi-tenancy in PostgreSQL, and the way to achieve multi-tenancy in PostgreSQL. What is a multi-tenant cluster? Why multi-tenant cluster is needed? PostgreSQL Provides multi-tenancy with the following - Shared Database, Shared Namespace - Separate Databases - Shared Database, Separate Namespace However multi-tenancy means more than this. - Issues with a multi-tenant cluster - What can be done and what can we do to make it easier. This talk will propose a multi tenanted architecture for PostgreSQL, to make it the database of choice in a cloud environment. Multi tenanted architecture is one of the key requirements for any software to be efficiently deployed in the cloud. As more and more databases are made available 'as-a-Service' in cloud offerings, it is necessary to take stock of the features in PostgreSQL to analyse how cloud friendly they are, especially for a multi-tenanted infrastructure. This talk will mainly focus on what functionalities are needed in PostgreSQL to make it truly cloud friendly. PostgreSQL needs to have the functionalities that will make it the database of choice for service providers in the cloud. This can be achieved within the current architecture of PostgreSQL by developing new features that will satisfy these requirements.