database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-30 21:42:05 +03:00
Code Activity

Stamp release 8.2.1. Update FAQs.

Browse Source
This commit is contained in:
Bruce Momjian
2007-01-05 20:55:29 +00:00
parent d6c8cdcceb
commit 4290bb4e0f
13 changed files with 125 additions and 76 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/FAQ
View File

@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Mon Dec 11 17:45:54 EST 2006 Last updated: Fri Jan 5 15:40:20 EST 2007
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
@ -171,7 +171,7 @@
1.6) What is the most recent release? 1.6) What is the most recent release?
The latest release of PostgreSQL is version 8.2.0. The latest release of PostgreSQL is version 8.2.1.
We plan to have a major release every year, with minor releases every We plan to have a major release every year, with minor releases every
few months. few months.

4
doc/FAQ_AIX
View File

@ -3,7 +3,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL
AIX Specific AIX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
======================================================= =======================================================
Last updated: $Date: 2006/12/11 22:48:07 $ Last updated: $Date: 2007/01/05 20:55:28 $
Topics Topics
@ -16,7 +16,7 @@ Topics
----- -----
From: Zeugswetter Andreas <ZeugswetterA@spardat.at> From: Zeugswetter Andreas <ZeugswetterA@spardat.at>
$Date: 2006/12/11 22:48:07 $ $Date: 2007/01/05 20:55:28 $
On AIX 4.3.2 PostgreSQL compiled with the native IBM compiler xlc On AIX 4.3.2 PostgreSQL compiled with the native IBM compiler xlc
(vac.C 5.0.1) passes all regression tests. Other versions of OS and (vac.C 5.0.1) passes all regression tests. Other versions of OS and

30
doc/FAQ_DEV
View File

@ -1,7 +1,7 @@
Developer's Frequently Asked Questions (FAQ) for PostgreSQL Developer's Frequently Asked Questions (FAQ) for PostgreSQL
Last updated: Mon Nov 13 23:18:46 EST 2006 Last updated: Thu Jan 4 16:00:00 EST 2007
Current maintainer: Bruce Momjian (bruce@momjian.us) Current maintainer: Bruce Momjian (bruce@momjian.us)
@ -30,6 +30,7 @@ General Questions
1.16) Where can I get a copy of the SQL standards? 1.16) Where can I get a copy of the SQL standards?
1.17) Where can I get technical assistance? 1.17) Where can I get technical assistance?
1.18) How do I get involved in PostgreSQL web site development? 1.18) How do I get involved in PostgreSQL web site development?
1.19) What is the timeline for the next major PostgreSQL release?
Technical Questions Technical Questions
@ -99,7 +100,9 @@ General Questions
both the internal implementation method you plan to use, and any both the internal implementation method you plan to use, and any
user-visible changes (new syntax, etc). For complex patches, it is user-visible changes (new syntax, etc). For complex patches, it is
important to get community feeback on your proposal before starting important to get community feeback on your proposal before starting
work. Failure to do so might mean your patch is rejected. work. Failure to do so might mean your patch is rejected. If your work
is being sponsored by a company, read this article for tips on being
more effective.
A web site is maintained for patches awaiting review, A web site is maintained for patches awaiting review,
http://momjian.postgresql.org/cgi-bin/pgpatches, and those that are http://momjian.postgresql.org/cgi-bin/pgpatches, and those that are
@ -225,7 +228,7 @@ General Questions
ccsym find standard defines made by your compiler ccsym find standard defines made by your compiler
copyright fixes copyright notices copyright fixes copyright notices
entab converts tabs to spaces, used by pgindent entab converts spaces to tabs, used by pgindent
find_static finds functions that could be made static find_static finds functions that could be made static
find_typedef finds typedefs in the source code find_typedef finds typedefs in the source code
find_badmacros finds macros that use braces incorrectly find_badmacros finds macros that use braces incorrectly
@ -796,3 +799,24 @@ typedef struct nameData
pgsql/data directory. The client profile file will be put in the pgsql/data directory. The client profile file will be put in the
client's current directory. Linux requires a compile with client's current directory. Linux requires a compile with
-DLINUX_PROFILE for proper profiling. -DLINUX_PROFILE for proper profiling.
2.9) What is the timeline for the next major PostgreSQL release?
The development schedule for the 8.3 release is:
March 1, 2007
Initial community review of all major feature patches
April 1, 2007
Feature freeze, all patches must be submitted for review and
application
mid-May, 2007
All patches applied, beta testing begins
July, 2007
Release of 8.3.0
Patches that appear after appropriate dates are typically not applied
but held for the next major release.

2
doc/FAQ_HPUX
View File

@ -3,7 +3,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL
HP-UX Specific HP-UX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
======================================================= =======================================================
last updated: $Date: 2006/12/11 22:48:07 $ last updated: $Date: 2007/01/05 20:55:28 $
current maintainer: Tom Lane (tgl@sss.pgh.pa.us) current maintainer: Tom Lane (tgl@sss.pgh.pa.us)
original author: Tom Lane (tgl@sss.pgh.pa.us) original author: Tom Lane (tgl@sss.pgh.pa.us)

2
doc/FAQ_IRIX
View File

@ -3,7 +3,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL
IRIX Specific IRIX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
======================================================= =======================================================
last updated: $Date: 2006/12/11 22:48:07 $ last updated: $Date: 2007/01/05 20:55:28 $
current maintainer: Luis Amigo (lamigo@atc.unican.es) current maintainer: Luis Amigo (lamigo@atc.unican.es)
original author: Luis Amigo (lamigo@atc.unican.es) original author: Luis Amigo (lamigo@atc.unican.es)

2
doc/FAQ_SCO
View File

@ -3,7 +3,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL
IRIX Specific IRIX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
======================================================= =======================================================
last updated: $Date: 2006/12/11 22:48:07 $ last updated: $Date: 2007/01/05 20:55:28 $
current maintainer: Billy G. Allie (Bill.Allie@mug.org) current maintainer: Billy G. Allie (Bill.Allie@mug.org)
original author: Andrew Merrill (andrew@compclass.com) original author: Andrew Merrill (andrew@compclass.com)

2
doc/FAQ_Solaris
View File

@ -3,7 +3,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL
Sun Solaris specific Sun Solaris specific
To be read in conjunction with the installation instructions. To be read in conjunction with the installation instructions.
============================================================ ============================================================
Last updated: $Date: 2006/12/11 22:48:07 $ Last updated: $Date: 2007/01/05 20:55:28 $
Contents: Contents:

2
doc/bug.template
View File

@ -31,7 +31,7 @@ System Configuration:
Operating System (example: Linux 2.4.18) : Operating System (example: Linux 2.4.18) :
PostgreSQL version (example: PostgreSQL 8.2) : PostgreSQL 8.2 PostgreSQL version (example: PostgreSQL 8.2.1): PostgreSQL 8.2.1
Compiler used (example: gcc 3.3.5) : Compiler used (example: gcc 3.3.5) :

4
doc/src/FAQ/FAQ.html
View File

@ -10,7 +10,7 @@
alink="#0000ff"> alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> <H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
<P>Last updated: Mon Dec 11 17:45:54 EST 2006</P> <P>Last updated: Fri Jan 5 15:40:20 EST 2007</P>
<P>Current maintainer: Bruce Momjian (<A href= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>) "mailto:bruce@momjian.us">bruce@momjian.us</A>)
@ -219,7 +219,7 @@
<H3 id="item1.6">1.6) What is the most recent release?</H3> <H3 id="item1.6">1.6) What is the most recent release?</H3>
<P>The latest release of PostgreSQL is version 8.2.0.</P> <P>The latest release of PostgreSQL is version 8.2.1.</P>
<P>We plan to have a major release every year, with minor releases <P>We plan to have a major release every year, with minor releases
every few months.</P> every few months.</P>

107
doc/src/FAQ/FAQ_DEV.html
View File

@ -13,7 +13,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for <H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1> PostgreSQL</H1>
<P>Last updated: Mon Nov 13 23:18:46 EST 2006</P> <P>Last updated: Thu Jan 4 16:00:00 EST 2007</P>
<P>Current maintainer: Bruce Momjian (<A href= <P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR> "mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR>
@ -55,6 +55,8 @@
assistance?<BR> assistance?<BR>
<A href="#item1.18">1.18</A>) How do I get involved in PostgreSQL web <A href="#item1.18">1.18</A>) How do I get involved in PostgreSQL web
site development?<BR> site development?<BR>
<A href="#item1.19">1.19</A>) What is the timeline for the next major
PostgreSQL release?<BR>
<H2>Technical Questions</H2> <H2>Technical Questions</H2>
@ -145,7 +147,9 @@
use, and any user-visible changes (new syntax, etc). For complex use, and any user-visible changes (new syntax, etc). For complex
patches, it is important to get community feeback on your proposal patches, it is important to get community feeback on your proposal
before starting work. Failure to do so might mean your patch is before starting work. Failure to do so might mean your patch is
rejected.</P> rejected. If your work is being sponsored by a company, read this
<a href="http://momjian.us/main/writings/pgsql/company_contributions/">
article</a> for tips on being more effective.</P>
<P>A web site is maintained for patches awaiting review, <P>A web site is maintained for patches awaiting review,
<a href="http://momjian.postgresql.org/cgi-bin/pgpatches"> <a href="http://momjian.postgresql.org/cgi-bin/pgpatches">
@ -300,7 +304,7 @@
ccsym find standard defines made by your compiler ccsym find standard defines made by your compiler
copyright fixes copyright notices copyright fixes copyright notices
entab converts tabs to spaces, used by pgindent entab converts spaces to tabs, used by pgindent
find_static finds functions that could be made static find_static finds functions that could be made static
find_typedef finds typedefs in the source code find_typedef finds typedefs in the source code
find_badmacros finds macros that use braces incorrectly find_badmacros finds macros that use braces incorrectly
@ -937,57 +941,78 @@
<H3 id="item2.7">2.7) What is CommandCounterIncrement()?</H3> <H3 id="item2.7">2.7) What is CommandCounterIncrement()?</H3>
<P>Normally, transactions can not see the rows they modify. This <P>Normally, transactions can not see the rows they modify.
allows <CODE>UPDATE foo SET x = x + 1</CODE> to work correctly.</P> This allows <CODE>UPDATE foo SET x = x + 1</CODE> to work
correctly.</P>
<P>However, there are cases where a transactions needs to see rows <P>However, there are cases where a transactions needs to see
affected in previous parts of the transaction. This is accomplished rows affected in previous parts of the transaction. This is
using a Command Counter. Incrementing the counter allows accomplished using a Command Counter. Incrementing the counter
transactions to be broken into pieces so each piece can see rows allows transactions to be broken into pieces so each piece can
modified by previous pieces. <I>CommandCounterIncrement()</I> see rows modified by previous pieces. <I>CommandCounterIncrement()</I>
increments the Command Counter, creating a new part of the increments the Command Counter, creating a new part of the
transaction.</P> transaction.</P>
<H3 id="item2.8">2.8) What debugging features are <H3 id="item2.8">2.8) What debugging features are available?</H3>
available?</H3>
<P>First, try running <I>configure</I> with the --enable-cassert <P>First, try running <I>configure</I> with the --enable-cassert
option, many <I>assert()</I>s monitor the progress of the backend option, many <I>assert()</I>s monitor the progress of the
and halt the program when something unexpected occurs.</P> backend and halt the program when something unexpected occurs.</P>
<P>The <I>postmaster</I> has a <I>-d</I> option that allows even more <P>The <I>postmaster</I> has a <I>-d</I> option that allows
detailed information to be reported. The <I>-d</I> option takes a even more detailed information to be reported. The <I>-d</I>
number that specifies the debug level. Be warned that high debug option takes a number that specifies the debug level. Be warned
level values generate large log files.</P> that high debug level values generate large log files.</P>
<P>If the <I>postmaster</I> is not running, you can actually run the <P>If the <I>postmaster</I> is not running, you can actually
<I>postgres</I> backend from the command line, and type your run the <I>postgres</I> backend from the command line, and type
<SMALL>SQL</SMALL> statement directly. This is recommended your <SMALL>SQL</SMALL> statement directly. This is recommended
<B>only</B> for debugging purposes. If you have compiled with debugging <B>only</B> for debugging purposes. If you have compiled with
symbols, you can use a debugger to see what is happening. Because debugging symbols, you can use a debugger to see what is
the backend was not started from <I>postmaster</I>, it is not happening. Because the backend was not started from <I>postmaster</I>,
running in an identical environment and locking/backend interaction it is not running in an identical environment and locking/backend
problems might not be duplicated.</P> interaction problems might not be duplicated.</P>
<P>If the <I>postmaster</I> is running, start <I>psql</I> in one <P>If the <I>postmaster</I> is running, start <I>psql</I> in
window, then find the <SMALL>PID</SMALL> of the <I>postgres</I> one window, then find the <SMALL>PID</SMALL> of the <I>postgres</I>
process used by <I>psql</I> using <CODE>SELECT pg_backend_pid()</CODE>. process used by <I>psql</I> using <CODE>SELECT pg_backend_pid()</CODE>.
Use a debugger to attach to the <I>postgres</I> <SMALL>PID</SMALL>. Use a debugger to attach to the <I>postgres</I> <SMALL>PID</SMALL>.
You can set breakpoints in the debugger and issue queries from the You can set breakpoints in the debugger and issue queries from
other. If you are looking to find the location that is generating the other. If you are looking to find the location that is
an error or log message, set a breakpoint at <I>errfinish</I>. generating an error or log message, set a breakpoint at
<I>errfinish</I>.
<I>psql</I>. If you are debugging <I>postgres</I> startup, you can <I>psql</I>. If you are debugging <I>postgres</I> startup, you
set PGOPTIONS="-W n", then start <I>psql</I>. This will cause startup can set PGOPTIONS="-W n", then start <I>psql</I>. This will
to delay for <I>n</I> seconds so you can attach to the process with cause startup to delay for <I>n</I> seconds so you can attach
the debugger, set any breakpoints, and continue through the startup to the process with the debugger, set any breakpoints, and
sequence.</P> continue through the startup sequence.</P>
<P>You can also compile with profiling to see what functions
are taking execution time. The backend profile files will be
deposited in the <I>pgsql/data</I> directory. The client profile
file will be put in the client's current directory. Linux
requires a compile with <I>-DLINUX_PROFILE</I> for proper
profiling.</P>
<H3 id="item2.9">2.9) What is the timeline for the next major
PostgreSQL release?<BR>
<P>The development schedule for the 8.3 release is:</P>
<DL>
<DD>March 1, 2007</DD>
<DT>Initial community review of all major feature patches</DT>
<DD>April 1, 2007</DD>
<DT>Feature freeze, all patches must be submitted for review and application</DT>
<DD>mid-May, 2007</DD>
<DT>All patches applied, beta testing begins</DT>
<DD>July, 2007</DD>
<DT>Release of 8.3.0</DT>
</DL>
<P>Patches that appear after appropriate dates are typically
not applied but held for the next major release.</P>
<P>You can also compile with profiling to see what functions are
taking execution time. The backend profile files will be deposited
in the <I>pgsql/data</I> directory. The client profile file will be
put in the client's current directory. Linux requires a compile with
<I>-DLINUX_PROFILE</I> for proper profiling.</P>
</BODY> </BODY>
</HTML> </HTML>

8
src/include/pg_config.h.win32
View File

@ -568,16 +568,16 @@
#define PACKAGE_NAME "PostgreSQL" #define PACKAGE_NAME "PostgreSQL"
/* Define to the full name and version of this package. */ /* Define to the full name and version of this package. */
#define PACKAGE_STRING "PostgreSQL 8.2" #define PACKAGE_STRING "PostgreSQL 8.2.1"
/* Define to the version of this package. */ /* Define to the version of this package. */
#define PACKAGE_VERSION "8.2" #define PACKAGE_VERSION "8.2.1"
/* PostgreSQL version as a string */ /* PostgreSQL version as a string */
#define PG_VERSION "8.2" #define PG_VERSION "8.2.1"
/* PostgreSQL version as a number */ /* PostgreSQL version as a number */
#define PG_VERSION_NUM 80200 #define PG_VERSION_NUM 80201
/* Define to the one symbol short name of this package. */ /* Define to the one symbol short name of this package. */
#define PACKAGE_TARNAME "postgresql" #define PACKAGE_TARNAME "postgresql"

8
src/interfaces/libpq/libpq.rc.in
View File

@ -1,8 +1,8 @@
#include <winver.h> #include <winver.h>
VS_VERSION_INFO VERSIONINFO VS_VERSION_INFO VERSIONINFO
FILEVERSION 8,2,0,0 FILEVERSION 8,2,1,0
PRODUCTVERSION 8,2,0,0 PRODUCTVERSION 8,2,1,0
FILEFLAGSMASK 0x3fL FILEFLAGSMASK 0x3fL
FILEFLAGS 0 FILEFLAGS 0
FILEOS VOS__WINDOWS32 FILEOS VOS__WINDOWS32
@ -15,13 +15,13 @@ BEGIN
BEGIN BEGIN
VALUE "CompanyName", "\0" VALUE "CompanyName", "\0"
VALUE "FileDescription", "PostgreSQL Access Library\0" VALUE "FileDescription", "PostgreSQL Access Library\0"
VALUE "FileVersion", "8.2.0\0" VALUE "FileVersion", "8.2.1\0"
VALUE "InternalName", "libpq\0" VALUE "InternalName", "libpq\0"
VALUE "LegalCopyright", "Copyright (C) 2005\0" VALUE "LegalCopyright", "Copyright (C) 2005\0"
VALUE "LegalTrademarks", "\0" VALUE "LegalTrademarks", "\0"
VALUE "OriginalFilename", "libpq.dll\0" VALUE "OriginalFilename", "libpq.dll\0"
VALUE "ProductName", "PostgreSQL\0" VALUE "ProductName", "PostgreSQL\0"
VALUE "ProductVersion", "8.2.0\0" VALUE "ProductVersion", "8.2.1\0"
END END
END END
BLOCK "VarFileInfo" BLOCK "VarFileInfo"

6
src/port/win32ver.rc
View File

@ -2,8 +2,8 @@
#include "pg_config.h" #include "pg_config.h"
VS_VERSION_INFO VERSIONINFO VS_VERSION_INFO VERSIONINFO
FILEVERSION 8,2,0,0 FILEVERSION 8,2,1,0
PRODUCTVERSION 8,2,0,0 PRODUCTVERSION 8,2,1,0
FILEFLAGSMASK 0x17L FILEFLAGSMASK 0x17L
FILEFLAGS 0x0L FILEFLAGS 0x0L
FILEOS VOS_NT_WINDOWS32 FILEOS VOS_NT_WINDOWS32
@ -17,7 +17,7 @@ BEGIN
VALUE "CompanyName", "PostgreSQL Global Development Group" VALUE "CompanyName", "PostgreSQL Global Development Group"
VALUE "FileDescription", FILEDESC VALUE "FileDescription", FILEDESC
VALUE "FileVersion", PG_VERSION VALUE "FileVersion", PG_VERSION
VALUE "LegalCopyright", "Portions Copyright (c) 1996-2006, PostgreSQL Global Development Group. Portions Copyright (c) 1994, Regents of the University of California." VALUE "LegalCopyright", "Portions Copyright (c) 1996-2007, PostgreSQL Global Development Group. Portions Copyright (c) 1994, Regents of the University of California."
VALUE "ProductName", "PostgreSQL" VALUE "ProductName", "PostgreSQL"
VALUE "ProductVersion", PG_VERSION VALUE "ProductVersion", PG_VERSION
END END