Remove references to pre-7.1; too old.
This commit is contained in:
parent
dddd8608b3
commit
c20ae1ce50
15
doc/FAQ
15
doc/FAQ
@ -1,7 +1,7 @@
|
|||||||
|
|
||||||
Frequently Asked Questions (FAQ) for PostgreSQL
|
Frequently Asked Questions (FAQ) for PostgreSQL
|
||||||
|
|
||||||
Last updated: Thu Jul 11 12:35:53 EDT 2002
|
Last updated: Thu Jul 11 12:37:48 EDT 2002
|
||||||
|
|
||||||
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
|
||||||
|
|
||||||
@ -803,7 +803,7 @@
|
|||||||
|
|
||||||
The ~ operator does regular expression matching, and ~* does
|
The ~ operator does regular expression matching, and ~* does
|
||||||
case-insensitive regular expression matching. The case-insensitive
|
case-insensitive regular expression matching. The case-insensitive
|
||||||
variant of LIKE is called ILIKE in PostgreSQL 7.1 and later.
|
variant of LIKE is called ILIKE.
|
||||||
|
|
||||||
Case-insensitive equality comparisons are normally expressed as:
|
Case-insensitive equality comparisons are normally expressed as:
|
||||||
SELECT *
|
SELECT *
|
||||||
@ -956,10 +956,9 @@ BYTEA bytea variable-length byte array (null-byte safe)
|
|||||||
|
|
||||||
4.18) Why do I get the error "ERROR: Memory exhausted in AllocSetAlloc()"?
|
4.18) Why do I get the error "ERROR: Memory exhausted in AllocSetAlloc()"?
|
||||||
|
|
||||||
If you are running a version older than 7.1, an upgrade may fix the
|
You probably have run out of virtual memory on your system, or your
|
||||||
problem. Also it is possible you have run out of virtual memory on
|
kernel has a low limit for certain resources. Try this before starting
|
||||||
your system, or your kernel has a low limit for certain resources. Try
|
postmaster:
|
||||||
this before starting postmaster:
|
|
||||||
ulimit -d 262144
|
ulimit -d 262144
|
||||||
limit datasize 256m
|
limit datasize 256m
|
||||||
|
|
||||||
@ -1012,8 +1011,8 @@ SELECT *
|
|||||||
|
|
||||||
4.23) How do I perform an outer join?
|
4.23) How do I perform an outer join?
|
||||||
|
|
||||||
PostgreSQL 7.1 and later supports outer joins using the SQL standard
|
PostgreSQL supports outer joins using the SQL standard syntax. Here
|
||||||
syntax. Here are two examples:
|
are two examples:
|
||||||
SELECT *
|
SELECT *
|
||||||
FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
|
FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
|
||||||
|
|
||||||
|
@ -14,7 +14,7 @@
|
|||||||
alink="#0000ff">
|
alink="#0000ff">
|
||||||
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
|
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
|
||||||
|
|
||||||
<P>Last updated: Thu Jul 11 12:35:53 EDT 2002</P>
|
<P>Last updated: Thu Jul 11 12:37:48 EDT 2002</P>
|
||||||
|
|
||||||
<P>Current maintainer: Bruce Momjian (<A href=
|
<P>Current maintainer: Bruce Momjian (<A href=
|
||||||
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
|
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
|
||||||
@ -1021,7 +1021,7 @@
|
|||||||
<P>The <I>~</I> operator does regular expression matching, and
|
<P>The <I>~</I> operator does regular expression matching, and
|
||||||
<I>~*</I> does case-insensitive regular expression matching. The
|
<I>~*</I> does case-insensitive regular expression matching. The
|
||||||
case-insensitive variant of <SMALL>LIKE</SMALL> is called
|
case-insensitive variant of <SMALL>LIKE</SMALL> is called
|
||||||
<SMALL>ILIKE</SMALL> in PostgreSQL 7.1 and later.</P>
|
<SMALL>ILIKE</SMALL>.</P>
|
||||||
|
|
||||||
<P>Case-insensitive equality comparisons are normally expressed
|
<P>Case-insensitive equality comparisons are normally expressed
|
||||||
as:</P>
|
as:</P>
|
||||||
@ -1229,10 +1229,9 @@ BYTEA bytea variable-length byte array (null-byte safe)
|
|||||||
<H4><A name="4.18">4.18</A>) Why do I get the error <I>"ERROR:
|
<H4><A name="4.18">4.18</A>) Why do I get the error <I>"ERROR:
|
||||||
Memory exhausted in AllocSetAlloc()"</I>?</H4>
|
Memory exhausted in AllocSetAlloc()"</I>?</H4>
|
||||||
|
|
||||||
<P>If you are running a version older than 7.1, an upgrade may fix
|
<P>You probably have run out of virtual memory on your system,
|
||||||
the problem. Also it is possible you have run out of virtual memory
|
or your kernel has a low limit for certain resources. Try this
|
||||||
on your system, or your kernel has a low limit for certain
|
before starting <I>postmaster</I>:</P>
|
||||||
resources. Try this before starting <I>postmaster</I>:</P>
|
|
||||||
<PRE>
|
<PRE>
|
||||||
ulimit -d 262144
|
ulimit -d 262144
|
||||||
limit datasize 256m
|
limit datasize 256m
|
||||||
@ -1301,8 +1300,8 @@ BYTEA bytea variable-length byte array (null-byte safe)
|
|||||||
|
|
||||||
<H4><A name="4.23">4.23</A>) How do I perform an outer join?</H4>
|
<H4><A name="4.23">4.23</A>) How do I perform an outer join?</H4>
|
||||||
|
|
||||||
<P>PostgreSQL 7.1 and later supports outer joins using the SQL
|
<P>PostgreSQL supports outer joins using the SQL standard syntax.
|
||||||
standard syntax. Here are two examples:</P>
|
Here are two examples:</P>
|
||||||
<PRE>
|
<PRE>
|
||||||
SELECT *
|
SELECT *
|
||||||
FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
|
FROM t1 LEFT OUTER JOIN t2 ON (t1.col = t2.col);
|
||||||
|
Loading…
x
Reference in New Issue
Block a user