Index: doc/src/FAQ/FAQ.html =================================================================== RCS file: /cvsroot/pgsql/doc/src/FAQ/FAQ.html,v retrieving revision 1.310 diff -c -c -r1.310 FAQ.html *** doc/src/FAQ/FAQ.html 30 May 2005 13:11:06 -0000 1.310 --- doc/src/FAQ/FAQ.html 10 Aug 2005 19:26:19 -0000 *************** *** 116,122 **** does not exist" errors when accessing temporary tables in PL/PgSQL functions?
4.20) What replication solutions are available?
!
--- 116,124 ---- does not exist" errors when accessing temporary tables in PL/PgSQL functions?
4.20) What replication solutions are available?
! 4.21) Why are my table and column names not ! recognized in my query?
!
*************** *** 613,618 **** --- 617,628 ----

The maximum table size and maximum number of columns can be quadrupled by increasing the default block size to 32k.

+

One limitation is that indexes can not be created on columns + longer than about 2,000 characters. Fortunately, such indexes are + rarely needed. Uniqueness is best guaranteed using another column + that is an MD5 hash of the long column, and full text indexing + allows for searching of words within the column.

+

4.5) How much database disk space is required to store data from a typical text file?

*************** *** 740,746 ****
      CREATE INDEX tabindex ON tab (lower(col));
  
!

4.9) In a query, how do I detect if a field is NULL? How can I sort on whether a field is NULL or not?

--- 750,761 ----
      CREATE INDEX tabindex ON tab (lower(col));
  
!

If the above index is created as UNIQUE, though ! the column can store upper and lowercase characters, it can not have ! identical values that differ only in case. To force a particular ! case to be stored in the column, use a CHECK ! constraint or a trigger.

!

4.9) In a query, how do I detect if a field is NULL? How can I sort on whether a field is NULL or not?

*************** *** 1000,1004 **** --- 1015,1036 ----

There are also commercial and hardware-based replication solutions available supporting a variety of replication models.

+ +

4.20) Why are my table and column names not + recognized in my query?

+ +

The most common cause is the use of double-quotes around table or + column names during table creation. When double-quotes are used, + table and column names (called identifiers) are stored case-sensitive, meaning you must use + double-quotes when referencing the names in a query. Some interfaces, + like pgAdmin, automatically double-quote identifiers during table + creation. So, for identifiers to be recognized, you must either: +