mirror of https://github.com/postgres/postgres
Subject: [PATCHES] Documentation update
This patch updates some of the documentation that comes with the
distribution. The following files are updated:
COPYRIGHT
README
doc/README.flex
doc/README.support
doc/bug.template
pull/50/head
Marc G. Fournier
29 years ago
parent
498d2d1edc
commit
b12241b2aa
@ -1,147 +0,0 @@ |
||||
From: ernst.molitor@uni-bonn.de |
||||
|
||||
Hi, |
||||
|
||||
thank you for the latest Postgres95 distribution! |
||||
|
||||
>does the createuser bug still persist, or have |
||||
>we finally worked that one out? |
||||
|
||||
As has been indication by Bruce Momjian, the createuser problem was |
||||
caused by a bug in flex 2.5.3 (which has been confirmed by Vern |
||||
Paxson, the flex maintainer - many thanks to them); the bug will be |
||||
fixed in flex 2.5.4. Vern Paxson has been so kind as to supply me with |
||||
a patch that will be part of the 2.5.4 release; I'm including it below |
||||
in case someone has installed flex 2.5.3 and doesn't want to go |
||||
back to 2.5.2... |
||||
|
||||
Regards, |
||||
|
||||
Ernst |
||||
--- |
||||
*** flex-2.5.3/flex.skl Sat May 25 21:02:33 1996 |
||||
--- flex.skl Tue Jul 2 16:35:49 1996 |
||||
*************** |
||||
*** 1,7 **** |
||||
/* A lexical scanner generated by flex */ |
||||
|
||||
/* Scanner skeleton version: |
||||
! * $Header: /cvsroot/pgsql/doc/Attic/README.flex,v 1.1.1.1 1996/08/18 22:14:17 scrappy Exp $ |
||||
*/ |
||||
|
||||
#define FLEX_SCANNER |
||||
--- 1,7 ---- |
||||
/* A lexical scanner generated by flex */ |
||||
|
||||
/* Scanner skeleton version: |
||||
! * $Header: /cvsroot/pgsql/doc/Attic/README.flex,v 1.1.1.1 1996/08/18 22:14:17 scrappy Exp $ |
||||
*/ |
||||
|
||||
#define FLEX_SCANNER |
||||
*************** |
||||
*** 783,789 **** |
||||
/* don't do the read, it's not guaranteed to return an EOF, |
||||
* just force an EOF |
||||
*/ |
||||
! yy_n_chars = 0; |
||||
|
||||
else |
||||
{ |
||||
--- 783,789 ---- |
||||
/* don't do the read, it's not guaranteed to return an EOF, |
||||
* just force an EOF |
||||
*/ |
||||
! yy_current_buffer->yy_n_chars = yy_n_chars = 0; |
||||
|
||||
else |
||||
{ |
||||
*************** |
||||
*** 838,843 **** |
||||
--- 838,845 ---- |
||||
/* Read in more data. */ |
||||
YY_INPUT( (&yy_current_buffer->yy_ch_buf[number_to_move]), |
||||
yy_n_chars, num_to_read ); |
||||
+ |
||||
+ yy_current_buffer->yy_n_chars = yy_n_chars; |
||||
} |
||||
|
||||
if ( yy_n_chars == 0 ) |
||||
*************** |
||||
*** 947,953 **** |
||||
|
||||
yy_cp += (int) (dest - source); |
||||
yy_bp += (int) (dest - source); |
||||
! yy_n_chars = yy_current_buffer->yy_buf_size; |
||||
|
||||
if ( yy_cp < yy_current_buffer->yy_ch_buf + 2 ) |
||||
YY_FATAL_ERROR( "flex scanner push-back overflow" ); |
||||
--- 949,956 ---- |
||||
|
||||
yy_cp += (int) (dest - source); |
||||
yy_bp += (int) (dest - source); |
||||
! yy_current_buffer->yy_n_chars = |
||||
! yy_n_chars = yy_current_buffer->yy_buf_size; |
||||
|
||||
if ( yy_cp < yy_current_buffer->yy_ch_buf + 2 ) |
||||
YY_FATAL_ERROR( "flex scanner push-back overflow" ); |
||||
*************** |
||||
*** 997,1009 **** |
||||
|
||||
switch ( yy_get_next_buffer() ) |
||||
{ |
||||
case EOB_ACT_END_OF_FILE: |
||||
{ |
||||
if ( yywrap() ) |
||||
- { |
||||
- yy_c_buf_p = yytext_ptr + offset; |
||||
return EOF; |
||||
- } |
||||
|
||||
if ( ! yy_did_buffer_switch_on_eof ) |
||||
YY_NEW_FILE; |
||||
--- 1000,1025 ---- |
||||
|
||||
switch ( yy_get_next_buffer() ) |
||||
{ |
||||
+ case EOB_ACT_LAST_MATCH: |
||||
+ /* This happens because yy_g_n_b() |
||||
+ * sees that we've accumulated a |
||||
+ * token and flags that we need to |
||||
+ * try matching the token before |
||||
+ * proceeding. But for input(), |
||||
+ * there's no matching to consider. |
||||
+ * So convert the EOB_ACT_LAST_MATCH |
||||
+ * to EOB_ACT_END_OF_FILE. |
||||
+ */ |
||||
+ |
||||
+ /* Reset buffer status. */ |
||||
+ yyrestart( yyin ); |
||||
+ |
||||
+ /* fall through */ |
||||
+ |
||||
case EOB_ACT_END_OF_FILE: |
||||
{ |
||||
if ( yywrap() ) |
||||
return EOF; |
||||
|
||||
if ( ! yy_did_buffer_switch_on_eof ) |
||||
YY_NEW_FILE; |
||||
*************** |
||||
*** 1017,1031 **** |
||||
case EOB_ACT_CONTINUE_SCAN: |
||||
yy_c_buf_p = yytext_ptr + offset; |
||||
break; |
||||
- |
||||
- case EOB_ACT_LAST_MATCH: |
||||
- #ifdef __cplusplus |
||||
- YY_FATAL_ERROR( |
||||
- "unexpected last match in yyinput()" ); |
||||
- #else |
||||
- YY_FATAL_ERROR( |
||||
- "unexpected last match in input()" ); |
||||
- #endif |
||||
} |
||||
} |
||||
} |
||||
--- 1033,1038 ---- |
||||
|
||||
@ -1,25 +1,235 @@ |
||||
PostgreSQL Support |
||||
|
||||
PostgreSQL Mailing Lists |
||||
|
||||
General Users/Questions |
||||
PostgreSQL is a freeware database server that is user |
||||
developed, maintained and supported. It was originally |
||||
known as Postgres, then as Postgres95. It is not ANSI |
||||
SQL compliant but it is getting closer with every release. |
||||
|
||||
This list is designed as a forum geared towards installation and usage |
||||
problems related to PostgreSQL, as well as a place to discuss general |
||||
SQL related problems. |
||||
For support on PostgreSQL, look in the following places: |
||||
|
||||
To subscribe, send a message of subscribe to: |
||||
questions-request@postgreSQL.org |
||||
* ftp://ftp.postgresql.org/pub/ |
||||
* http://www.postgresql.org/ |
||||
* Text files in directory /usr/src/pgsql. |
||||
* Text files in directory /usr/src/pgsql/docs. |
||||
* The FAQ, located in /usr/src/pgsql/doc/FAQ. The |
||||
latest version may be found at |
||||
http://www.postgresql.org/ under documentation. |
||||
* Digests of all of the PostgreSQL mailing lists are |
||||
archived at ftp://ftp.postgresql.org/pub/majordomo/. |
||||
* The mailing list, which are described below. |
||||
|
||||
Hackers/Development Discussions |
||||
|
||||
This list is where bugs reports and server improvements are discussed, |
||||
providing the developers with an area seperate from the general |
||||
questions, while allowing both end-users and administrators a chance to |
||||
join in and follow the discussions. |
||||
Support Mailing Lists: |
||||
|
||||
To subscribe, send a message of subscribe to: |
||||
hackers-request@postgreSQL.org |
||||
* Announce for announcements. |
||||
* Ports for OS-specific bugs. |
||||
* Bugs for other unsolved bugs. |
||||
* Questions for general discussion. |
||||
|
||||
All the mailing lists are archived, with archives available at: |
||||
ftp://ftp.postgreSQL.org/pub/majordomo |
||||
|
||||
Mailing Lists for Developers: |
||||
|
||||
* Hackers for server internals discussion. |
||||
* Docs for the documentation project. |
||||
* Patches for patches and discussion. |
||||
* Mirrors for mirror site announcements. |
||||
|
||||
|
||||
Descriptions of PostgreSQL Mailing Lists |
||||
|
||||
Announce |
||||
|
||||
* This is an announcement list pertaining to |
||||
PostgreSQL and various third party software. |
||||
* To post, send mail to pgsql-announce@postgresql.org. |
||||
* To subscribe or unsubscribe from the list, send mail |
||||
to pgsql-announce-request@postgresql.org. The body |
||||
of the message should contain the single line |
||||
subscribe or unsubscribe. |
||||
* If you hate getting many mail messages per day then |
||||
you should consider a digest (where you receive |
||||
multiple messages to the list as one message to |
||||
you). To subscribe or unsubscribe from the digested |
||||
list, send mail to |
||||
pgsql-announce-digest-request@postgresql.org. The |
||||
body of the message should contain the single line |
||||
subscribe or unsubscribe. |
||||
|
||||
Ports |
||||
|
||||
* This list is for porting related and platform |
||||
specific discussions. |
||||
* If PostgreSQL failed to compile on your computer |
||||
then fill out the form typically located at |
||||
/usr/src/pgsql/doc/bug.template and mail it here. |
||||
* If you get PostgreSQL running on an unsupported |
||||
platform, tell us how you did it here. And before |
||||
you attempt the port, check the archives for this |
||||
area to see if someone else has already done it. |
||||
* To post, send mail to pgsql-ports@postgresql.org. |
||||
* To subscribe or unsubscribe from the list, send mail |
||||
to pgsql-ports-request@postgresql.org. The body of |
||||
the message should contain the single line subscribe |
||||
or unsubscribe. |
||||
* If you hate getting many mail messages per day then |
||||
you should consider a digest (where you receive |
||||
multiple messages to the list as one message to |
||||
you). To subscribe or unsubscribe from the digested |
||||
list, send mail to |
||||
pgsql-ports-digest-request@postgresql.org. The body |
||||
of the message should contain the single line |
||||
subscribe or unsubscribe. |
||||
|
||||
Bugs |
||||
|
||||
* If PostgreSQL failed to compile on your computer, |
||||
report this to pgsql-ports@postgresql.org. Do not |
||||
report it here. |
||||
* If you find bug, fill out the form typically located |
||||
at /usr/src/pgsql/doc/bug.template and mail it here. |
||||
* If you not only found the problem but solved it and |
||||
generated a patch then also mail it to the patches |
||||
list. |
||||
* To post, send mail to pgsql-bugs@postgresql.org. |
||||
* To subscribe or unsubscribe from the list, send mail |
||||
to pgsql-bugs-request@postgresql.org. The body of |
||||
the message should contain the single line subscribe |
||||
or unsubscribe. |
||||
* If you hate getting many mail messages per day then |
||||
you should consider a digest (where you receive |
||||
multiple messages to the list as one message to |
||||
you). To subscribe or unsubscribe from the digested |
||||
list, send mail to |
||||
pgsql-bugs-digest-request@postgresql.org. The body |
||||
of the message should contain the single line |
||||
subscribe or unsubscribe. |
||||
|
||||
Questions |
||||
|
||||
* This is a general discussion area for users. |
||||
* Outside of compile, acceptance test and bug |
||||
problems, most new users who don't want to |
||||
contribute to development or documentation will |
||||
probably only be interested in this mailing list. |
||||
* All non-bug related questions regarding PostgreSQL's |
||||
version of SQL should be restricted to this area. |
||||
* All installation related questions that do not |
||||
involve bugs or failed compiles should be restricted |
||||
to this area. |
||||
* Please note that many of the developers monitor this |
||||
area. |
||||
* To post, send mail to |
||||
pgsql-questions@postgresql.org. |
||||
* To subscribe or unsubscribe from the list, send mail |
||||
to pgsql-questions-request@postgresql.org. The body |
||||
of the message should contain the single line |
||||
subscribe or unsubscribe. |
||||
* If you hate getting many mail messages per day then |
||||
you should consider a digest (where you receive |
||||
multiple messages to the list as one message to |
||||
you). To subscribe or unsubscribe from the digested |
||||
list, send mail to |
||||
pgsql-questions-digest-request@postgresql.org. The |
||||
body of the message should contain the single line |
||||
subscribe or unsubscribe. |
||||
|
||||
Hackers |
||||
|
||||
* The PostgreSQL developer's team lives here. |
||||
* This list is for the discussion of current |
||||
development issues, problems and bugs and the |
||||
discussion of proposed new features. |
||||
* If people in the other lists don't know the answer |
||||
to a question and it is likely that only a developer |
||||
will know the answer, you may re-post that question |
||||
here. You must try elsewhere first! |
||||
* To post, send mail to pgsql-hackers@postgresql.org. |
||||
* To subscribe or unsubscribe from the list, send mail |
||||
to pgsql-hackers-request@postgresql.org. The body of |
||||
the message should contain the single line subscribe |
||||
or unsubscribe. |
||||
* If you hate getting many mail messages per day then |
||||
you should consider a digest (where you receive |
||||
multiple messages to the list as one message to |
||||
you). To subscribe or unsubscribe from the digested |
||||
list, send mail to |
||||
pgsql-hackers-digest-request@postgresql.org. The |
||||
body of the message should contain the single line |
||||
subscribe or unsubscribe. |
||||
Docs |
||||
|
||||
* The PostgreSQL documentation team lives here and at |
||||
http://www.postgresql.org/~dunlop. |
||||
* If you come up with SQL examples that are not shown |
||||
in the current man pages or manuals, please let us |
||||
know here. |
||||
* If you are looking for "secret" manuals, check here. |
||||
Old manuals that are mostly not relevant or works in |
||||
progress that are not ready for general distribution |
||||
might be mentione here. But please don't ask us. |
||||
Check the archives for examples. |
||||
* The team leader is J. Douglas Dunlop. |
||||
* Please note that suggestions regarding the web site |
||||
should be directed to our webmaster at |
||||
webmaster@postgresql.org |
||||
* To post, send mail to pgsql-docs@postgresql.org. |
||||
* To subscribe or unsubscribe from the list, send mail |
||||
to pgsql-docs-request@postgresql.org. The body of |
||||
the message should contain the single line subscribe |
||||
or unsubscribe. |
||||
* If you hate getting many mail messages per day then |
||||
you should consider a digest (where you receive |
||||
multiple messages to the list as one message to |
||||
you). To subscribe or unsubscribe from the digested |
||||
list, send mail to |
||||
pgsql-docs-digest-request@postgresql.org. The body |
||||
of the message should contain the single line |
||||
subscribe or unsubscribe. |
||||
|
||||
Patches |
||||
|
||||
* Mail patches you created to this area. Explain what |
||||
the patches do, and which source tree they are meant |
||||
to be applied against. |
||||
* This list also contains notices (normally from |
||||
scrappy@hub.org) that the patch has been applied are |
||||
posted here. |
||||
* Discussion of any problems that a recent patch |
||||
caused should also be here. |
||||
* Please use a context diff (diff -c) when submitting |
||||
patches. It would also be helpful if you checked |
||||
whether your patches apply against the latest |
||||
development source. |
||||
* To post, send mail to pgsql-patches@postgresql.org. |
||||
* To subscribe or unsubscribe from the list, send mail |
||||
to pgsql-patches-request@postgresql.org. The body of |
||||
the message should contain the single line subscribe |
||||
or unsubscribe. |
||||
* If you hate getting many mail messages per day then |
||||
you should consider a digest (where you receive |
||||
multiple messages to the list as one message to |
||||
you). To subscribe or unsubscribe from the digested |
||||
list, send mail to |
||||
pgsql-patches-digest-request@postgresql.org. The |
||||
body of the message should contain the single line |
||||
subscribe or unsubscribe. |
||||
|
||||
Mirrors |
||||
|
||||
* This is an announcement list for mirror sites. |
||||
* If you don't run a PostgreSQL mirror site, please |
||||
don't post here. |
||||
* To post, send mail to pgsql-mirrors@postgresql.org. |
||||
* To subscribe or unsubscribe from the list, send mail |
||||
to pgsql-mirrors-request@postgresql.org. The body of |
||||
the message should contain the single line subscribe |
||||
or unsubscribe. |
||||
* If you hate getting many mail messages per day then |
||||
you should consider a digest (where you receive |
||||
multiple messages to the list as one message to |
||||
you). To subscribe or unsubscribe from the digested |
||||
list, send mail to |
||||
pgsql-mirrors-digest-request@postgresql.org. The |
||||
body of the message should contain the single line |
||||
subscribe or unsubscribe. |
||||
|
||||
Loading…
Reference in new issue