aboutsummaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2001-10-13 05:27:05 +0000
committerBruce Momjian <bruce@momjian.us>2001-10-13 05:27:05 +0000
commit657d0044b0550265f9b03ee4b723044779b4322d (patch)
tree2f665b6d524a2cca7f5ae14db168aaa7f937b6c1 /doc/FAQ
parent46712990bd80eae04d31764072da47bc93a5360a (diff)
downloadpostgresql-657d0044b0550265f9b03ee4b723044779b4322d.tar.gz
postgresql-657d0044b0550265f9b03ee4b723044779b4322d.zip
Update FAQ.
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/FAQ b/doc/FAQ
index 027d5aae86e..334143ce5b2 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Fri Oct 12 23:53:35 EDT 2001
+ Last updated: Sat Oct 13 01:26:55 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?