Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
9392c405
Commit
9392c405
authored
22 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Update CHAR().
parent
13437d1e
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/FAQ
+5
-5
5 additions, 5 deletions
doc/FAQ
with
5 additions
and
5 deletions
doc/FAQ
+
5
−
5
View file @
9392c405
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Sun Jan 12
09:58:38
EST 2003
Last updated: Sun Jan 12
13:36:11
EST 2003
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
...
...
@@ -820,10 +820,10 @@
Type Internal Name Notes
--------------------------------------------------
"char" char 1 character
CHAR(n) bpchar blank padded to the specified fixed length
VARCHAR(n) varchar size specifies maximum length, no padding
CHAR(n) bpchar blank padded to the specified fixed length
TEXT text no specific upper limit on length
"char" char one character
BYTEA bytea variable-length byte array (null-byte safe)
You will see the internal name when examining system catalogs and in
...
...
@@ -834,9 +834,9 @@ BYTEA bytea variable-length byte array (null-byte safe)
space used is slightly greater than the declared size. However, these
data types are also subject to compression or being stored out-of-line
by TOAST, so the space on disk might also be less than expected.
VARCHAR(n) is best when storing variable-length strings
but
it limits
VARCHAR(n) is best when storing variable-length strings
and
it limits
how long a string can be. TEXT is for strings of unlimited length,
maximum
1
gigabyte.
with a
maximum
of one
gigabyte.
CHAR(n) is for storing strings that are all the same length. CHAR(n)
pads with blanks to the specified length, while VARCHAR(n) only stores
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment