From 7d03a83f4d0736ba869fa6f93973f7623a27038a Mon Sep 17 00:00:00 2001 From: Robert Haas Date: Wed, 19 Feb 2014 08:35:23 -0500 Subject: Add a pg_lsn data type, to represent an LSN. Robert Haas and Michael Paquier --- doc/src/sgml/datatype.sgml | 32 ++++++++++++++++++++++++++++++++ 1 file changed, 32 insertions(+) (limited to 'doc/src') diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index 30fd9bb598d..00ccbe1bb5f 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -180,6 +180,12 @@ geometric path on a plane + + pg_lsn + + PostgreSQL Log Sequence Number + + point @@ -4504,6 +4510,32 @@ SELECT * FROM pg_attribute + + <acronym>pg_lsn Type</acronym> + + + pg_lsn + + + + The pg_lsn data type can be used to store LSN (Log Sequence + Number) data which is a pointer to a location in the XLOG. This type is a + representation of XLogRecPtr and an internal system type of + PostgreSQL. + + + + Internally, an LSN is a 64-bit integer, representing a byte position in + the write-ahead log stream. It is printed as two hexadecimal numbers of + up to 8 digits each, separated by a slash; for example, + 16/B374D848. The pg_lsn type supports the + standard comparison operators, like = and + >. Two LSNs can be subtracted using the + - operator; the result is the number of bytes separating + those write-ahead log positions. + + + Pseudo-Types -- cgit v1.2.3