Skip to main content
Documents
Basic SyntaxMath FunctionsDate FunctionsJSON FunctionsDatabasesTables & Schema ManagementString FunctionsTriggersIndexes

PostgreSQL Aliases (AS)

In PostgreSQL, an alias is a temporary name assigned to a table or column for the duration of a SQL query. The `AS` keyword is used to create aliases, enhancing readability and simplifying complex queries.

Usage

Aliases are utilized to rename a column or a table within a query, making it easier to reference and improving overall query clarity. The basic syntax involves the `AS` keyword followed by the desired alias name.

Syntax

For column aliases:

SELECT column_name AS alias_name
FROM table_name;

For table aliases:

SELECT column_name
FROM table_name AS alias_name;

In these examples, `column_name AS alias_name` renames the column, and `table_name AS alias_name` renames the table within the context of the query. Note that the `AS` keyword is optional in PostgreSQL, but using it can enhance readability.

Examples

1. Basic Column Alias

SELECT first_name AS fname
FROM employees;

This example assigns an alias `fname` to the `first_name` column, making the column's purpose clearer in the results.

2. Table Alias

SELECT e.first_name, e.last_name
FROM employees AS e;

Here, the table `employees` is aliased as `e`, allowing for shorter references to its columns in the query.

3. Complex Query with Aliases

SELECT e.first_name AS "First Name", e.last_name AS "Last Name", d.department_name AS "Department"
FROM employees AS e
JOIN departments AS d ON e.department_id = d.department_id;

In this example, both columns and tables are aliased to clarify the query and organize the output with descriptive headers.

4. Aliases in a Subquery

SELECT sub.emp_count, d.department_name
FROM (SELECT department_id, COUNT(*) AS emp_count FROM employees GROUP BY department_id) AS sub
JOIN departments AS d ON sub.department_id = d.department_id;

This example demonstrates the use of an alias in a subquery, which helps in organizing and referencing the subquery results in the main query.

Tips and Best Practices

  • Use descriptive aliases. Choose aliases that clearly describe the data, making the results easier to understand.
  • Avoid reserved keywords. Do not use PostgreSQL reserved keywords as aliases to prevent syntax errors.
  • Consistent aliasing. Maintain a consistent aliasing convention throughout your queries to improve maintainability.
  • Use quotes for spaces. If an alias contains spaces or special characters, enclose it in double quotes.