Preamble
PostgreSQL Alias can be used to create a temporary name for tables or columns. Column aliases are used to make it easier to read column headers in a set of results.
Table aliases are used to shorten your SQL code to make it easier to read or when you connect yourself (i.e. enumerate the same table more than once in the FROM statement).
Column alias syntax in PostgreSQL
column_name [ AS ] alias_name
or:
The syntax for table alias in PostgreSQL
table_name [ AS ] alias_name
Parameters or alias arguments
- column_name – the original name of the column to which you want to define an alias.
- table_name – the original name of the table you want to define an alias for.
- AS – Optional. Most programmers will specify AS when determining the column name alias, but not when determining the table name alias. Whether you specify an AS or not does affect an alias in PostgreSQL. This is a personal choice in PostgreSQL, in contrast to other databases. (Our examples will use AS when you specify a column name alias, but omit AS when you specify a table name alias).
- alias_name – A temporary name that can be given to a column or table.
Note:
- If alias_name contains spaces, you must enclose alias_name in quotes.
- It is acceptable to use spaces when creating a column name alias. However, it is usually not recommended to use spaces when creating a table name alias.
- alias_name is only allowed within an SQL statement.
Alias column
Usually, aliases are used to facilitate the reading of column headers in the resulting set. For example, when using the function MAX, you can use the result alias MAX.
For example, you can use an alias of the result of a function MAX:
SELECT sales_person, MAX(commission) AS highest
FROM sales
GROUP BY sales_person;
In this example, we called the MAX(commission) field as high. The result is that the highest will be displayed as a header for the second column when returning the result set. Since there were no spaces in our alias_name, we do not have to quote alias_name.
It would however be quite acceptable to write this example using quotes as follows:
SELECT sales_person, MAX(commission) AS "highest"
FROM sales
GROUP BY sales_person;
Next, let’s look at an example where we need to enclose alias_name in quotes.
For example:
SELECT sales_person, MAX(commission) AS "high commission"
FROM sales
GROUP BY sales_person;
In this example, we called the MAX(commission) field as “high commission”. Since there are spaces in this alias_name, “high commission” must be enclosed in quotes.
Alias table
When you create an alias for a table, this happens either because you plan to specify the same table name more than once in the FROM statement (i.e. Self join), or you want to shorten the table name to make the SQL statement shorter and more readable.
Let’s take a look at an example of how to create a table alias.
For example:
SELECT p.product_id, p.product_name, inventory.quantity
FROM products p
INNER JOIN inventory
ON p.product_id = inventory.product_id
ORDER BY p.product_name ASC, inventory.quantity DESC;
In this example, we created an alias for the products table called p. Within this SQL statement, we can now refer to the products table as p.
When creating table aliases, there is no need to create aliases for all tables listed in the FROM statement. You can create aliases for any or all tables in the following way.
For example, we could change our example above and create an alias for the table.
SELECT p.product_id, p.product_name, i.quantity
FROM products p
INNER JOIN inventory i
ON p.product_id = i.product_id
ORDER BY p.product_name ASC, i.quantity DESC;
We now have an alias for the inventory table with the name i, and an alias for the products table with the name p.
Tutorial; Alias In PostgreSQL
About Enteros
Enteros offers a patented database performance management SaaS platform. It proactively identifies root causes of complex business-impacting database scalability and performance issues across a growing number of clouds, RDBMS, NoSQL, and machine learning database platforms.
The views expressed on this blog are those of the author and do not necessarily reflect the opinions of Enteros Inc. This blog may contain links to the content of third-party sites. By providing such links, Enteros Inc. does not adopt, guarantee, approve, or endorse the information, views, or products available on such sites.
Are you interested in writing for Enteros’ Blog? Please send us a pitch!
RELATED POSTS
How to Enable Intelligent Wealth Growth with Enteros Database Analytics, RevOps Automation, and Gen AI
- 24 June 2026
- Software Engineering
Introduction Wealth management and investment organizations are entering a new era defined by data-driven decision-making, AI-powered advisory systems, and highly automated operational environments. As client expectations grow and financial markets become more dynamic, firms must continuously improve performance, efficiency, and personalization to remain competitive. Modern wealth organizations now operate complex ecosystems that include: Portfolio management … Continue reading “How to Enable Intelligent Wealth Growth with Enteros Database Analytics, RevOps Automation, and Gen AI”
How to Improve Financial Cost Visibility with Enteros Database Management Platform and Cost Attribution Analytics
Introduction The financial services industry is rapidly evolving as banks, insurance companies, fintech platforms, and investment firms modernize their digital infrastructure to support real-time transactions, data-driven decision-making, and highly personalized customer experiences. Modern financial organizations operate complex ecosystems that include: Core banking systems Digital payment platforms Investment and trading systems Risk management applications Fraud detection … Continue reading “How to Improve Financial Cost Visibility with Enteros Database Management Platform and Cost Attribution Analytics”
How AI-Driven Database Monitoring Enhances Business Continuity and Resilience
In today’s always-on digital economy, business continuity and operational resilience have become essential for enterprise success. Organizations depend heavily on digital systems to support customer interactions, financial transactions, supply chain operations, analytics, internal workflows, and real-time decision-making. Any disruption to these systems can lead to significant financial loss, operational inefficiencies, and reputational damage. At the … Continue reading “How AI-Driven Database Monitoring Enhances Business Continuity and Resilience”
Reducing Application Latency with Intelligent Database Performance Management
In today’s digital economy, application speed is directly tied to business success. Whether users are shopping online, using banking applications, streaming content, accessing SaaS platforms, or interacting with enterprise systems, they expect fast and seamless experiences. Even minor delays can impact user satisfaction, engagement, and revenue. Application latency has become one of the most important … Continue reading “Reducing Application Latency with Intelligent Database Performance Management”