1
0
mirror of https://github.com/postgres/postgres.git synced 2025-06-14 18:42:34 +03:00
Commit Graph

13017 Commits

Author SHA1 Message Date
ab71c20fdf Update FAQ. 2001-01-28 17:39:44 +00:00
677fe55c12 Update FAQ. 2001-01-28 15:18:45 +00:00
b72ca55ed5 Update FAQ. 2001-01-27 20:19:34 +00:00
94bf45265f Make into appendix, correct some items. 2001-01-27 11:12:53 +00:00
dc7a0009f0 Add permission check for CHECKPOINT. 2001-01-27 10:19:52 +00:00
76beb79d27 in the tutorial, chapter 2., "Relational Data Model Formalities"
(sql490.htm), there is

"set of all k-tuples v1, v2, ... vk, such that v1 [isin] D1, v1 [isin] D1"

i assume it should be
"set of all k-tuples v1, v2, ... vk, such that v1 [isin] D1, v2 [isin] D2"

Divide by Zero
2001-01-27 05:07:28 +00:00
a60537240f Update FAQ. 2001-01-27 04:38:54 +00:00
2696cf0412 Update FAQ. 2001-01-27 04:35:16 +00:00
1c63587f24 Clean up markup, add description of contrib/array operators by Joel Burton
<jburton@scw.org>.
2001-01-26 23:40:39 +00:00
61737a7b47 Add some links from data type chapter to section on literal constants. 2001-01-26 22:04:22 +00:00
7b9dc71405 WAL documentation, from Oliver Elphick and Vadim Mikheev. 2001-01-24 23:15:19 +00:00
43bac8406a Update based on documentation written by Vadim Mikheev and Oliver Elphick. 2001-01-24 21:56:23 +00:00
623bf843d2 Change Copyright from PostgreSQL, Inc to PostgreSQL Global Development Group. 2001-01-24 19:43:33 +00:00
87070ccc13 It looks Ok, but it has one unnecessary step. There is no need to do the "mv
privkey.pem cert.pem.pw" if you just use "privkey.pem" in the following
openssl command (e.g. openssl rsa -in privkey.pem -out cert.pem".
But there is nothing wrong with it as it is now, as far as I can see.


//Magnus
2001-01-24 15:19:36 +00:00
80d24370e0 Oops, had .o file in there. 2001-01-24 05:06:15 +00:00
a939e97451 Update 2001-01-24 03:40:33 +00:00
fc031fbe5c Update FAQ. 2001-01-23 01:11:34 +00:00
c805491792 Update FAQ. 2001-01-23 01:11:06 +00:00
c0bb21b369 Update FAQ. 2001-01-23 01:00:55 +00:00
21a3857f1f Rip out table expression section from SQL syntax chapter and develop it
into new chapter on query (SELECT) syntax.  In the end this should become
a narrative and example-filled counterpart to the SELECT reference page.
2001-01-22 23:34:33 +00:00
60b282fd26 Put back old MS FAQ> 2001-01-22 22:54:07 +00:00
56f5f2bf82 Update FAQ. 2001-01-22 17:20:12 +00:00
0fada37f5d Update FAQ. 2001-01-22 16:35:35 +00:00
7e0919136a Minor fixes. 2001-01-22 16:11:17 +00:00
505cdd5873 Update FAQ. 2001-01-22 06:27:41 +00:00
5f93794f1e Update FAQ. 2001-01-22 05:56:26 +00:00
64b3af90f1 Add. 2001-01-22 03:47:22 +00:00
bf01c7983b Make Kevin Lo's MS FAQ the default. 2001-01-22 03:33:55 +00:00
d90eb434e4 Update FAQ. 2001-01-21 22:16:56 +00:00
4f34f55d3d Description of table expressions, including join syntax, from Robert B.
Easter <reaster@comptechnews.com>, heavily massaged by me.  Also cleaned up
value expressions a bit.
2001-01-21 22:02:01 +00:00
11d9d2cfaa Update FAQ. 2001-01-21 05:01:57 +00:00
a2405d5554 Get rid of initdb -t bugs by the simple expedient of getting rid of
initdb -t.  This option is obsoleted by 7.1's ability to drop and
recreate template1 during normal operation.
2001-01-20 22:09:24 +00:00
74bbe8097d Replace some oldish, non-SQL'ish elements with more standard forms. (cast
syntax, type names, function names, etc.)
2001-01-20 20:59:29 +00:00
923513b52f Move anoncvs to top of docs, then put cvs tree. Hope that is OK. Seems
more logical.
2001-01-20 04:16:55 +00:00
d128852358 In the Programmer's Guide, the sample code for accessing large objects
from libpq has two functions with memory leaks.

The functions pickout() and overwrite() malloc space for buf which is
never freed.

See
http://www.postgresql.org/users-lounge/docs/7.0/programmer/largeobjects3207.htm

This problem is also in the 6.5 docs at
http://www.postgresql.org/users-lounge/docs/6.5/programmer/x3184.htm

Nishad Prakash
2001-01-20 00:05:54 +00:00
1073123baa Update docs to explain that 7.1 locks down LC_COLLATE and LC_CTYPE at
initdb time.  A few copy-editing cleanups, too.
2001-01-19 04:47:50 +00:00
6439de1752 Fix incorrect placeholder name in example. 2001-01-18 07:18:39 +00:00
7705581e49 Replace contraction with long form. Cosmetic only. 2001-01-18 07:11:36 +00:00
392793b1ac Functions -> Function's 2001-01-17 22:13:33 +00:00
9a342d2035 There are misprints in postgres doc., in :
Chapter 10. PL/pgSQL - SQL Procedural Language (c40914117.htm)

Statements
...
(resulting in a PL/pgSQL internal SELECT).
But there are cases where someone isn't interested int
-----------------------------------------(have to be)-->
But there are cases where someone isn't interested in
     the functions result.

 RAISE level format''
--(have to be)-->
 RAISE level 'format'
2001-01-17 16:34:34 +00:00
1ced7f3b30 Adjust file names. 2001-01-15 21:17:27 +00:00
027f144e39 Terminology cleanup: class -> table, instance -> row, attribute -> column,
etc.
2001-01-13 23:58:55 +00:00
526427f6d3 Add information about bit types. Adjust some other things to promote
SQL type names over internal type names.
2001-01-13 18:34:51 +00:00
2a6c08228f New shell for the to be written CHECKPOINT documentation, so the summary
shows up in psql now.
2001-01-13 03:11:12 +00:00
a32542a1c0 Update information about compiling extension modules. 2001-01-12 22:15:32 +00:00
359459a44d Bring CREATE TABLE syntax synopsis into line with reality; update a
bunch of old or poorly-worded documentation.
2001-01-12 05:06:40 +00:00
f906597e50 Apply proper sql.sgml change. 2001-01-09 16:05:21 +00:00
777137b7a9 Attached is a doc patch for doc/src/sgml/sql.sgml.
It adds information about SQL JOIN that is implemented in 7.1.

--
-------- Robert B. Easter
2001-01-09 15:48:18 +00:00
5d42c0f3ac A patch for doc/src/sgml/plsql.sgml to add a little more info about PL/pgSQL
EXECUTE.

--
-------- Robert B. Easter
2001-01-09 15:26:16 +00:00
df389d161d Approaching the current documentation from a position of ignorance, I
find it ambiguous.  I propose something along the lines of the
following patch to clarify it.  Thanks.

(Alternatively, perhaps the code could maintain a count of nested
calls to SPI_connect/SPI_finish.  But I didn't try to write that
patch.)

Ian Lance Taylor
2001-01-09 14:23:40 +00:00