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
657d0044
Commit
657d0044
authored
23 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Update FAQ.
parent
46712990
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/FAQ
+5
-5
5 additions, 5 deletions
doc/FAQ
doc/src/FAQ/FAQ.html
+8
-6
8 additions, 6 deletions
doc/src/FAQ/FAQ.html
with
13 additions
and
11 deletions
doc/FAQ
+
5
−
5
View file @
657d0044
Frequently Asked Questions (FAQ) for PostgreSQL
Last updated:
Fri
Oct 1
2 23:53:3
5 EDT 2001
Last updated:
Sat
Oct 1
3 01:26:5
5 EDT 2001
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
...
...
@@ -791,10 +791,10 @@ BYTEA bytea variable-length byte array (null-safe)
by TOAST, so the space on disk might also be less than expected.
CHAR() is best when storing strings that are usually the same length.
VARCHAR() is best when storing variable-length strings
,
but
you want
to limit
how long a string can be. TEXT is for strings of unlimited
length,
maximum 1 gigabyte. BYTEA is for storing binary data,
particularly
values that include NULL bytes.
VARCHAR() is best when storing variable-length strings but
it limits
how long a string can be. TEXT is for strings of unlimited
length,
maximum 1 gigabyte. BYTEA is for storing binary data,
particularly
values that include NULL bytes.
4.16.1) How do I create a serial/auto-incrementing field?
...
...
This diff is collapsed.
Click to expand it.
doc/src/FAQ/FAQ.html
+
8
−
6
View file @
657d0044
...
...
@@ -12,7 +12,7 @@
alink=
"#0000FF"
>
<H1>
Frequently Asked Questions (FAQ) for PostgreSQL
</H1>
<P>
Last updated:
Fri
Oct 1
2 23:53:3
5 EDT 2001
</P>
<P>
Last updated:
Sat
Oct 1
3 01:26:5
5 EDT 2001
</P>
<P>
Current maintainer: Bruce Momjian (
<A
href=
"mailto:pgman@candle.pha.pa.us"
>
pgman@candle.pha.pa.us
</A>
)
<BR>
...
...
@@ -1003,11 +1003,13 @@ BYTEA bytea variable-length byte array (null-safe)
stored out-of-line by
<SMALL>
TOAST
</SMALL>
, so the space on disk
might also be less than expected.
</P>
<P>
CHAR() is best when storing strings that are usually the
same length. VARCHAR() is best when storing variable-length strings,
but you want to limit how long a string can be. TEXT is for strings
of unlimited length, maximum 1 gigabyte. BYTEA is for storing
binary data, particularly values that include NULL bytes.
</P>
<P><SMALL>
CHAR()
</SMALL>
is best when storing strings that are
usually the same length.
<SMALL>
VARCHAR()
</SMALL>
is best when
storing variable-length strings but it limits how long a
string can be.
<SMALL>
TEXT
</SMALL>
is for strings of unlimited
length, maximum 1 gigabyte.
<SMALL>
BYTEA
</SMALL>
is for storing
binary data, particularly values that include
<SMALL>
NULL
</SMALL>
bytes.
</P>
<H4><A
name=
"4.16.1"
>
4.16.1
</A>
) How do I create a
serial/auto-incrementing field?
</H4>
...
...
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