Preamble
Below is a list of data types available in PostgreSQL, which includes string, numeric, and date/time type.
String data types
Below are String data types in PostgreSQL :
|
Syntax of data types
|
Explanation
|
|---|---|
|
char (size)
|
Where size is the number of characters to store. A string of fixed lengths. Space is added to the right to the size of the characters.
|
|
character (size)
|
Where size is the number of characters to store. A string of fixed lengths. Space is added to the right to the size of the characters.
|
|
var symbol (size)
|
Where size is the number of characters to store. A string of variable lengths.
|
|
character varying(size)
|
Where size is the number of characters to store. A string of variable lengths.
|
|
text
|
The string of variable length.
|
Numerical data types
Below are the numeric data types in PostgreSQL:
|
Syntax of data types
|
Explanation
|
|---|---|
|
bit(size)
|
Bit string of fixed length,
where size is the length of a string of bits. |
|
varbit(size) bit varying(size)
|
Bit string of variable length,
where size is the length of a string of bits. |
|
smallint
|
Equivalent to int2.
2-byte integer with a sign. |
|
int
|
Equivalent to int4.
4-byte integer with a sign. |
|
integer
|
Equivalent to int4.
4-byte integer with a sign. |
|
bigint
|
A large integer value, equivalent to int8.
An 8-byte integer with a sign. |
|
smallserial
|
A small integer value with auto-increment equivalent to serial2.
2-byte integer with a sign, autoincrement. |
|
serial
|
Auto-incremental integer value, equivalent to serial4.
4-byte integer with a sign, auto-incremental. |
|
bigserial
|
Large auto-incremental integer value equivalent to serial8.
8-byte integer with a sign, auto-incremental. |
|
numeric(m,d)
|
Where m is the total number of digits, and d is the number after the decimal fraction.
|
|
double precision
|
8 bytes, double-precision, floating-point number.
|
|
real
|
4-byte floating-point single-precision number.
|
|
money
|
Cost of currency.
|
|
bool
|
Logical logical data type – true or false.
|
|
boolean
|
Logical logical data type – true or false.
|
Date/Time Types of data
Below is the date/time of the data types in PostgreSQL:
|
Syntax of data types
|
Explanation
|
|---|---|
|
date
|
Displayed as “YYYY-MM-DD”.
|
|
timestamp
|
Displayed as «YYYY-MM-DD HH:MM:SS».
|
|
timestamp without time zone
|
Displayed as «YYYY-MM-DD HH:MM:SS».
|
|
timestamp with time zone
|
Displayed as «YYYY-MM-DD HH:MM:SS-TZ».
Equivalent to the timestamptz. |
|
time
|
Displayed as «HH:MM:SS» without a time zone.
|
|
time without time zone
|
Displayed as «HH:MM:SS» without a time zone.
|
|
time with time zone
|
Displayed as «HH:MM:SS-TZ» with the time zone.
Equivalent to the time zone. |
Understanding Advanced Datatypes 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
Unlocking RevOps Efficiency in the Banking World with AIOps-Powered Database Technology and Root Cause Analysis—Driven by Enteros
- 15 September 2025
- Database Performance Management
Introduction The banking sector has long been a pioneer in adopting cutting-edge technologies to maintain security, efficiency, and customer trust. From mobile banking apps and real-time payments to fraud detection systems and risk management models, financial institutions operate on massive volumes of data and complex database infrastructures. But with this dependency comes a unique set … Continue reading “Unlocking RevOps Efficiency in the Banking World with AIOps-Powered Database Technology and Root Cause Analysis—Driven by Enteros”
Driving Technology Sector Growth with Enteros: AI-Powered Database Performance, Cloud FinOps, and Next-Gen Database Software
Introduction The technology sector is at the heart of global digital transformation. From software-as-a-service (SaaS) providers to enterprise IT vendors, cloud-native startups, and global hyperscalers, the industry is both the builder and consumer of massive-scale digital infrastructure. To remain competitive, technology companies must ensure optimal database performance, leverage the power of artificial intelligence (AI), adopt … Continue reading “Driving Technology Sector Growth with Enteros: AI-Powered Database Performance, Cloud FinOps, and Next-Gen Database Software”
NFT drops failing: how DB lags ruin million-dollar launches
When Seconds Decide Millions Imagine this: a highly anticipated NFT collection drops at midnight. Thousands of wallets flood in, bidding wars begin, prices spike. And then—suddenly—the marketplace freezes. Transactions hang, bids vanish, collectors complain on Twitter, and the brand’s reputation tanks overnight. This isn’t a rare story in Web3. It’s a database story. In this … Continue reading “NFT drops failing: how DB lags ruin million-dollar launches”
911 call centers under DB overload: response delayed
Introduction In emergencies, every second is the difference between life and death. Yet as 911 call centers shift to fully digital systems, they face an invisible but growing threat: database performance. When the data layer lags, critical decisions—from dispatching ambulances to locating callers—can be delayed, putting lives at risk. How Databases Power Emergency Response Modern … Continue reading “911 call centers under DB overload: response delayed”