[DOCS] IPv6 all-balls address

2011-03-18 Thread Bruce Momjian
I have applied the attached patch which documents the all-balls IPv6
address.

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

  + It's impossible for everything to be true. +
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
new file mode 100644
index a2c0494..c05805b
*** a/doc/src/sgml/client-auth.sgml
--- b/doc/src/sgml/client-auth.sgml
*** hostnossl  database172.20.143.89/32 for a single host, or
 172.20.143.0/24 for a small network, or
 10.6.0.0/16 for a larger one.
!0.0.0.0/0 (all balls) represents all addresses.
 To specify a single host, use a CIDR mask of 32 for IPv4 or
 128 for IPv6.  In a network address, do not omit trailing zeroes.

--- 241,249 
 172.20.143.89/32 for a single host, or
 172.20.143.0/24 for a small network, or
 10.6.0.0/16 for a larger one.
!0.0.0.0/0 (all balls) represents all
!IPv4 addresses, and :: represents
!all IPv6 addresses.
 To specify a single host, use a CIDR mask of 32 for IPv4 or
 128 for IPv6.  In a network address, do not omit trailing zeroes.


-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs


[DOCS] pg_last_xact_replay_timestamp clarification

2011-03-18 Thread Bruce Momjian
The attached, applied patch documents that the timestamp returned by
pg_last_xact_replay_timestamp is the time on the _primary_ that the
transaction was generated.

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

  + It's impossible for everything to be true. +
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
new file mode 100644
index 8b5c3c5..3106a0f
*** a/doc/src/sgml/func.sgml
--- b/doc/src/sgml/func.sgml
*** postgres=# SELECT * FROM pg_xlogfile_nam
*** 14219,14225 
 timestamp with time zone
 Get timestamp of last transaction replayed during recovery.
  This is the time at which the commit or abort WAL record for that
! transaction was generated.
  If no transactions have been replayed during recovery, this function
  returns NULL.  Otherwise, if recovery is still in progress this will
  increase monotonically.  If recovery has completed then this value will
--- 14219,14225 
 timestamp with time zone
 Get timestamp of last transaction replayed during recovery.
  This is the time at which the commit or abort WAL record for that
! transaction was generated on the primary.
  If no transactions have been replayed during recovery, this function
  returns NULL.  Otherwise, if recovery is still in progress this will
  increase monotonically.  If recovery has completed then this value will

-- 
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs