Index: cube.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/cube.sgml,v
retrieving revision 1.2
diff -c -r1.2 cube.sgml
*** cube.sgml 11 Nov 2007 14:23:18 -0000 1.2
--- cube.sgml 2 Dec 2007 23:32:29 -0000
***************
*** 353,358 ****
--- 353,364 ----
+ cube(text)
+ Takes text input and returns a cube. This is useful for making
+ cubes from computed strings.
+
+
+
cube(float8) returns cube
This makes a one dimensional cube with both coordinates the same.
If the type of the argument is a numeric type other than float8 an
Index: intarray.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/intarray.sgml,v
retrieving revision 1.2
diff -c -r1.2 intarray.sgml
*** intarray.sgml 12 Nov 2007 01:37:34 -0000 1.2
--- intarray.sgml 2 Dec 2007 23:32:29 -0000
***************
*** 12,20 ****
Current implementation provides index support for one-dimensional array of
! int4's - gist__int_ops, suitable for small and medium size of arrays (used on
default), and gist__intbig_ops for indexing large arrays (we use superimposed
! signature with length of 4096 bits to represent sets).
--- 12,21 ----
Current implementation provides index support for one-dimensional array of
! integers: gist__int_ops, suitable for small and medium size of arrays (used by
default), and gist__intbig_ops for indexing large arrays (we use superimposed
! signature with length of 4096 bits to represent sets). There is also a
! non-default gin__int_ops for GIN indexes on integer arrays.
Index: pageinspect.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/pageinspect.sgml,v
retrieving revision 1.1
diff -c -r1.1 pageinspect.sgml
*** pageinspect.sgml 10 Nov 2007 23:30:46 -0000 1.1
--- pageinspect.sgml 2 Dec 2007 23:32:29 -0000
***************
*** 32,46 ****
A page image obtained with get_raw_page should be passed as argument:
! test=# SELECT * FROM page_header(get_raw_page('pg_class',0));
! lsn | tli | flags | lower | upper | special | pagesize | version
! ----------+-----+-------+-------+-------+---------+----------+---------
! 0/3C5614 | 1 | 1 | 216 | 256 | 8192 | 8192 | 4
! (1 row)
! The returned columns correspond to the fields in the PageHeaderData-struct,
! see src/include/storage/bufpage.h for more details.
--- 32,45 ----
A page image obtained with get_raw_page should be passed as argument:
! regression=# SELECT * FROM page_header(get_raw_page('pg_class',0));
! lsn | tli | flags | lower | upper | special | pagesize | version | prune_xid
! -----------+-----+-------+-------+-------+---------+----------+---------+-----------
! 0/24A1B50 | 1 | 1 | 232 | 368 | 8192 | 8192 | 4 | 0
! The returned columns correspond to the fields in the PageHeaderData struct.
! See src/include/storage/bufpage.h for more details.
Index: pgbench.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/pgbench.sgml,v
retrieving revision 1.2
diff -c -r1.2 pgbench.sgml
*** pgbench.sgml 11 Nov 2007 14:23:18 -0000 1.2
--- pgbench.sgml 2 Dec 2007 23:32:29 -0000
***************
*** 379,384 ****
--- 379,399 ----
Variables can also be defined by using -D option.
+
+
+
+ \sleep num [us|ms|s] - Causes script execution to sleep for the
+ specified duration of microseconds (us), milliseconds (ms) or the default
+ seconds (s).
+
+
+ Example:
+
+
+ \setrandom millisec 1000 2500
+ \sleep : millisec ms
+
Index: pgrowlocks.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/pgrowlocks.sgml,v
retrieving revision 1.2
diff -c -r1.2 pgrowlocks.sgml
*** pgrowlocks.sgml 11 Nov 2007 14:23:18 -0000 1.2
--- pgrowlocks.sgml 2 Dec 2007 23:32:29 -0000
***************
*** 102,108 ****
Example
! pgrowlocks returns the following data type:
Here is a sample execution of pgrowlocks:
--- 102,108 ----
Example
! pgrowlocks returns the following columns:
Here is a sample execution of pgrowlocks:
Index: standby.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/Attic/standby.sgml,v
retrieving revision 1.1
diff -c -r1.1 standby.sgml
*** standby.sgml 10 Nov 2007 23:30:46 -0000 1.1
--- standby.sgml 2 Dec 2007 23:32:30 -0000
***************
*** 7,15 ****
! pg_standby is a production-ready program that can be used
! to create a Warm Standby server. Other configuration is required as well,
! all of which is described in the main server manual.
The program is designed to be a wait-for restore_command,
--- 7,15 ----
! pg_standby allows the creation of a Warm Standby server.
! Other configuration is required as well, all of which is described in the
! main server manual.
The program is designed to be a wait-for restore_command,
***************
*** 18,24 ****
you could configure pg_standby in the following way:
! restore_command = 'pg_standby archiveDir %f %p'
which would be sufficient to define that files will be restored from
--- 18,24 ----
you could configure pg_standby in the following way:
! restore_command = 'pg_standby archiveDir %f %p %r'
which would be sufficient to define that files will be restored from
***************
*** 72,83 ****
with the pg_standby command usage as
! pg_standby [OPTION]... [ARCHIVELOCATION] [NEXTWALFILE] [XLOGFILEPATH]
When used within the restore_command the %f and %p macros
will provide the actual file and path required for the restore/recovery.
Options
--- 72,96 ----
with the pg_standby command usage as
! pg_standby [OPTION]... ARCHIVELOCATION NEXTWALFILE XLOGFILEPATH [RESTARTWALFILE]
When used within the restore_command the %f and %p macros
will provide the actual file and path required for the restore/recovery.
+
+
+ pg_standby assumes that ARCHIVELOCATION
+ is a directory accessible by the server-owning user.
+
+
+ If RESTARTWALFILE is specified, typically by using the
+ %r option, then all files prior to this file will be
+ removed from ARCHIVELOCATION. This then minimises the
+ number of files that need to be held, whilst at the same time maintaining
+ restart capability. This capability additionally assumes that
+ ARCHIVELOCATION directory is writable.
+
Options
***************
*** 95,102 ****
-k numfiles
! Cleanup files in the archive so that we maintain no more
! than this many files in the archive.
You should be wary against setting this number too low,
--- 108,118 ----
-k numfiles
! Cleanup files in the archive so that we maintain no more than this
! many files in the archive. This parameter will be silently ignored if
! RESTARTWALFILE is specified, since that
! specification method is more accurate in determining the correct
! cut-off point in archive.
You should be wary against setting this number too low,
***************
*** 110,117 ****
--- 126,142 ----
on either primary or standby.
+ Setting numfiles to be zero will disable deletion
+ of files from ARCHIVELOCATION.
+
+
If in doubt, use a large value or do not set a value at all.
+
+ If you specify neither RESTARTWALFILE nor -k, then -k 0 will
+ be assumed, i.e. keep all files in archive. Default=0,
+ Min=0
+
***************
*** 122,130 ****
WAL files will remain in archive
! Link is more efficient, but the default is copy to
! allow you to maintain the WAL archive for recovery
! purposes as well as high-availability.
This option uses the Windows Vista command mklink
--- 147,156 ----
WAL files will remain in archive
! Link is more efficient, but the default is copy to allow you to
! maintain the WAL archive for recovery purposes as well as
! high-availability. The default setting is not necessarily recommended,
! consult the main database server manual for discussion.
This option uses the Windows Vista command mklink
***************
*** 145,151 ****
we will wait 5 secs, 10 secs then 15 secs before reporting
the failure back to the database server. This will be
interpreted as and end of recovery and the Standby will come
! up fully as a result. Default=3
--- 171,177 ----
we will wait 5 secs, 10 secs then 15 secs before reporting
the failure back to the database server. This will be
interpreted as and end of recovery and the Standby will come
! up fully as a result. Default=3 Min=0
***************
*** 156,162 ****
if the file to be restored is available in the archive yet.
The default setting is not necessarily recommended,
consult the main database server manual for discussion.
! Default=5
--- 182,188 ----
if the file to be restored is available in the archive yet.
The default setting is not necessarily recommended,
consult the main database server manual for discussion.
! Default=5, Min=1, Max=60
***************
*** 176,183 ****
the maximum number of seconds to wait for the next file,
after which recovery will end and the Standby will come up.
The default setting is not necessarily recommended,
! consult the main database server manual for discussion.
! Default=0
--- 202,210 ----
the maximum number of seconds to wait for the next file,
after which recovery will end and the Standby will come up.
The default setting is not necessarily recommended,
! consult the main database server manual for discussion. A setting of
! zero means wait forever.
! Default=0, Min=0
***************
*** 193,198 ****
--- 220,251 ----
+ Supported versions
+
+ pg_standby is designed to work with PostgreSQL 8.2 and
+ and later. It is currently compatible across minor changes between the way
+ 8.3 and 8.2 operate.
+
+
+ PostgreSQL 8.3 provides the %r command line substitution,
+ designed to let pg_standby know the last file it needs to
+ keep. If the last parameter is omitted, no error is generated, allowing
+ pg_standby to function correctly with PostgreSQL 8.2
+ also. With PostgreSQL 8.2, the -k option must be used if
+ archive cleanup is required. This option remains available in 8.3.
+
+
+
+
+ Additional design notes
+
+ The use of a move command seems like it would be a good idea, but this would
+ prevent recovery from being restartable. Also, the last WAL file is always
+ requested twice from the archive.
+
+
+
+
Examples
***************
*** 228,235 ****
*not* in the restore_command, in 8.2, 8.1, 8.0 on Windows.
! restore_command = 'pg_standby -c -d -s 5 -w 0 -t C:\pgsql.trigger.5442
! ..\archive %f %p 2>> standby.log'
which will
--- 281,287 ----
*not* in the restore_command, in 8.2, 8.1, 8.0 on Windows.
! restore_command = 'pg_standby -c -d -s 5 -w 0 -t C:\pgsql.trigger.5442 ..\archive %f %p 2>> standby.log'
which will