I use schemas to separate subdomains. Answer from j_priest on reddit.com
PostgreSQL Wiki
wiki.postgresql.org › wiki › Database_Schema_Recommendations_for_an_Application
Database Schema Recommendations for an Application - PostgreSQL wiki
The recommendation is to create a single database with multiple named schemas. This is different than a common (and older) practice of creating multiple databases and storing the objects within the "public" schema.
Mydbops
mydbops.com › blog › postgresql-schema-guide
PostgreSQL Schema Guide: Structure, Security & | Mydbops
October 22, 2025 - Since no schema was specified, PostgreSQL placed the users table in the public schema. To avoid clutter and improve security, it’s a best practice to create and use custom schemas.
How are folks using schemas?
I use schemas to separate subdomains. More on reddit.com
26
21
January 7, 2024database - Postgres Schema Best Practices - Stack Overflow
I'm newer to Postgres, having used MySQL almost exclusively in the past I'm looking to move to Postgres for its more enterprise like features and SQL compliance. However Postgres is structured much More on stackoverflow.com
security - Achieving best practice schema and permissions management on PostgreSQL - Database Administrators Stack Exchange
I want to allow (human) users to ... schema, and have no other privileges on the instance (other than to connect of course). I think there are some "sub-optimal" practices already in place here, which might be common to inexperienced PostgreSQL users, and this question addresses what they are and how they should best be ... More on dba.stackexchange.com
Best practices for very large databases ?
Ok, this is operational size or „baby has grown to this size on data” ? First questions would be: Do you have any data retention policies in place ? Does this company really need instant access to all this data ? Is there a business reason (reverse data search requirements) for DB this big ? Generally best case scenario is dataset fits into memory… All queries need to account that they’re run against a monster table sizes so “limit as early as possible” policy is a must. We have a 11TB MySQL RDS roller coaster - it’s funny from time to time. More on reddit.com
25
21
June 10, 202307:37
PostgreSQL Schema Explained - A Beginner’s Guide - Mydbops Podcast ...
07:15
What is PostgreSQL Schema Management? Ankush Sir | Learnomate ...
14:22
PostgreSQL Schemas || Schemas Advanced Options in PostgreSQL || ...
40:49
Best Practices | Postgres.FM 136 | #PostgreSQL #Postgres podcast ...
18:37
Creating and Managing PostgreSQL Schemas - YouTube
39:40
How to perform Postgres schema changes in production with zero ...
PostgreSQL
postgresql.org › docs › current › ddl-schemas.html
PostgreSQL: Documentation: 18: 5.10. Schemas
May 14, 2026 - By default such tables (and other objects) are automatically put into a schema named “public”. Every new database contains such a schema. Thus, the following are equivalent: CREATE TABLE products ( ... ); ... CREATE TABLE public.products ( ... ); Qualified names are tedious to write, and it's often best not to wire a particular schema name into applications anyway.
Reddit
reddit.com › r/postgresql › how are folks using schemas?
r/PostgreSQL on Reddit: How are folks using schemas?
January 7, 2024 -
Hi PostgreSQL subreddit,
I'm curious how folks are leveraging schemas, and preferably an at-scale use case/example.
I my several years, and handful of companies, of software engineering, I've only had to work with a simple public schema, and it has worked fine, but I'm curious how others are using schemas, if at all.
Thanks in advance!
CLIMB
climbtheladder.com › 10-postgresql-schema-best-practices
10 PostgreSQL Schema Best Practices - CLIMB
July 16, 2025 - This means that any objects created in this schema are accessible by everyone, which can lead to security issues and data integrity problems. To avoid these issues, it’s best practice to create separate schemas for each user or application.
TigerData
tigerdata.com › learn › postgresql-performance-tuning-designing-and-implementing-database-schema
PostgreSQL Tuning: Database Schema Design | Tiger Data
February 11, 2026 - AWS Timestream for InfluxDB Alternative: When You Need to Look FurtherHow to Migrate from AWS Timestream to PostgreSQL: A Technical GuideHow to Choose a Database: A Decision Framework for Modern ApplicationsPostgreSQL Performance Tuning: Key ParametersA Guide to Scaling PostgreSQLHandling Large Objects in PostgresGuide to PostgreSQL PerformanceDetermining the Optimal Postgres Partition SizeNavigating Growing PostgreSQL Tables With Partitioning (and More)SQL/JSON Data Model and JSON in SQL: A PostgreSQL PerspectiveHow to Use PostgreSQL for Data TransformationPostgreSQL Performance Tuning: Designing and Implementing Your Database SchemaPostgreSQL Performance Tuning: Optimizing Database IndexesWhen to Consider Postgres PartitioningDesigning Your Database Schema: Wide vs. Narrow Postgres TablesBest Practices for Time-Series Data Modeling: Single or Multiple Partitioned Table(s) a.k.a.
Reintech
reintech.io › blog › best-practices-database-schema-design-postgresql
Best Practices for Database Schema Design in PostgreSQL | Reintech media
June 3, 2024 - When designing a PostgreSQL database schema, it's essential to normalize your data appropriately; choose suitable data types; use proper indexing; implement constraints; avoid premature optimization; maintain thorough documentation; consider ...
DB Vis
dbvis.com › thetable › schemas-in-postgresql
Schemas in PostgreSQL: Best Practices of PostgreSQL Schemas
March 11, 2024 - Schemas allow you to organize database objects for easy maintenance. Since PostgreSQL supports the use of multiple schemas within one database, if we have a database X with two schemas (schema_1 and schema_2) and a table X1, accessing the table through two different schemas becomes easy.
Postgraphile
postgraphile.org › postgresql schema design
PostgreSQL Schema Design | PostGraphile
You can name your schema anything, we recommend naming your schema after your app. This way if you are working on multiple apps in the same database (this might only realistically happen in development), you can easily query the databases of the different apps.
Medium
iniakunhuda.medium.com › introduction-to-postgresql-schemas-a-practical-guide-8089b351b953
Introduction to PostgreSQL Schemas: A Practical Guide | by Miftahul Huda | Medium
February 26, 2025 - Just as you wouldn’t want to mix all the furniture from different apartments in one space, you might not want to mix tables from different parts of your application in a single schema. The “public” schema that comes with PostgreSQL by default is like the building’s lobby — it’s accessible to everyone by default, but you might want to keep some things in more private spaces.
Swiftorial
swiftorial.com › tutorials › postgresql › best practices › schema design best practices
Schema Design Best Practices | Best Practices | Postgresql Tutorial
August 22, 2025 - Optimize schema design for performance by understanding query patterns and workload.
ER Flow
erflow.io › home › blog › postgresql schema design guide: best practices and tools
PostgreSQL Schema Design Guide: Best Practices and Tools | ER Flow
May 26, 2026 - This guide covers the PostgreSQL-specific schema design choices that matter most in production: which data types to use, how to index effectively, how to structure schemas with namespaces, and how tools like ER Flow can streamline the design process.
TigerData
tigerdata.com › learn › how-to-design-postgresql-database-two-schema-examples
How to Design Your PostgreSQL Database | Tiger Data
February 11, 2026 - Designing Your Database Schema: Wide vs. Narrow Postgres Tables · Best Practices for Time-Series Data Modeling: Single or Multiple Partitioned Table(s) a.k.a.
Mikealche
mikealche.com › software-development › a-humble-guide-to-database-schema-design
A humble guide to database schema design – Mike Alche
For example for names like “Juan Martin Del Potro” I believe that “Juan Martin” belongs to the first_name field and “Del Potro” to the last_name field. Of course this isn’t ideal: you could have a middle_name column, or second_last_name column. However in here you can read about all the variations a name can take. So at some point you’ll need to decide between precision and practicality.
TigerData
tigerdata.com › learn › designing-your-database-schema-wide-vs-narrow-postgres-tables
Designing Your Database Schema | Tiger Data
February 11, 2026 - AWS Timestream for InfluxDB Alternative: When You Need to Look FurtherHow to Migrate from AWS Timestream to PostgreSQL: A Technical GuideHow to Choose a Database: A Decision Framework for Modern ApplicationsPostgreSQL Performance Tuning: Key ParametersA Guide to Scaling PostgreSQLHandling Large Objects in PostgresGuide to PostgreSQL PerformanceDetermining the Optimal Postgres Partition SizeNavigating Growing PostgreSQL Tables With Partitioning (and More)SQL/JSON Data Model and JSON in SQL: A PostgreSQL PerspectiveHow to Use PostgreSQL for Data TransformationPostgreSQL Performance Tuning: Designing and Implementing Your Database SchemaPostgreSQL Performance Tuning: Optimizing Database IndexesWhen to Consider Postgres PartitioningDesigning Your Database Schema: Wide vs. Narrow Postgres TablesBest Practices for Time-Series Data Modeling: Single or Multiple Partitioned Table(s) a.k.a.
Sling Academy
slingacademy.com › article › best-practices-for-schema-design-in-postgresql-with-timescaledb
Best Practices for Schema Design in PostgreSQL with TimescaleDB - Sling Academy
Finally, always maintain documentation of your database schema. Documenting helps future developers understand your database structure and makes transitioning or scaling easier. By following these best practices, your PostgreSQL and TimescaleDB schemas will be better equipped to handle extensive analytic workloads efficiently and reliably.
E2E Networks
e2enetworks.com › blog › best-practices-for-postgresql-database
Best Practices for PostgreSQL Database (2022) | E2E Networks
May 20, 2022 - Therefore, you should always implement foreign keys, checks, and normalisation practices to store data in the database. Denormalisation should be applied only when you cannot store the data in normalised format with an acceptable level of complexity.
Airbyte
airbyte.com › home › data engineering resources › create database schema in postgresql
How to Create a Database Schema in PostgreSQL: An Ultimate Guide | Airbyte
September 1, 2025 - A well-designed PostgreSQL schema is essential for efficiently organizing data and enabling scalable database architectures. Modern tooling including zero-downtime migration frameworks like pgroll, robust CI/CD pipelines, and schema-aware replication platforms like Airbyte elevates schema management from a risky, manual process to a competitive advantage. Organizations adopting these practices report reduced deployment risk, faster development cycles, and improved operational efficiency.