docs/pg_timestamp.html

<!DOCTYPE html PUBLIC "-//W3C//DTD html 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>pg_timestamp</title>
<link rel="home" title="pg_timestamp" href="index.html">
<link rel="stylesheet" TYPE="text/css"href="style.css">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>

<body>
<h1 id="pg_timestamp">pg_timestamp</h1>
<div class="navigation">
  <a href="index.html">Top</a> &gt;
  <a href="pg_timestamp.html">pg_timestamp</a>
<div>
<hr />

<p>
pg_timestamp ia an optional tool to skip parsing overhead of timestamp string.
This is involved in a pg_bulkload package.
</p>

<h3>pg_timestamp_in</h3>
<p>
This user-defined function provides very fast loading of timestamp type data.
For the speed, instead, the format of the timestamp data must satisfy the 
following 19byte format:
</p>

<pre><code>2007-01-01 12:34:56</code></pre>
<ul>
	  <li>Year/Month/Day/Hour/Minute/Second, each must be represented using only digits (0x30 to 0x39, no month name, no AM/PM, etc.).
	  <li>Only a hyphen (0x2d) can be used (and must be used) to separate year, month and day.
	  <li>Single space (0x20) must appear between the day and the hour.
	  <li>Hour, minute and second must be separated using single colon (0x3a)
	    respectively.
	  <li>No additional spaces and tabs are allowed.
</ul>

<h2>Installation</h2>
<p>
Installation sequence is shown below. As a preliminary, the permissions of directories of PostgreSQL server should be set correctly.
</p>
<pre><code>
$ cd [directory where postgresql-8.2or3.X.tar.gz is untared]/contrib/
$ tar zxvf pg_bulkload-2.3.X.tar.gz
$ cd pg_bulkload
$ make
$ make install
$ postgresql start
$ psql -f $PGHOME/share/contrib/pg_timestamp.sql database_name
</code></pre>


<h2>Reminder</h2>
<p>
  Timestamp value with timezone attribute is outside the scope of pg_timestamp_in. 
  If you provide data in such format, you must use usual 
  PostgreSQL feature to read data.   In this case, you may need longer duration
  to load.  Although pg_timestamp_in provide much faster data loading for 
  timestamp data, it replaces usual PostgreSQL's internal function used to read
  timestamp data.   That is, use of pg_timestamp_in influences the data symtax 
  for PostgreSQL's SQL statements such as <code>INSERT</code>, <code>COPY</code>, and <code>UPDATE</code>.   To avoid 
  such influence, users have to use pg_timestamp_in only in the data loading, 
  and uninstall pg_timestamp_in.
</p>

<hr />
<div class="navigation">
  <a href="index.html">Top</a> &gt;
  <a href="pg_timestamp.html">pg_timestamp</a>
<div>
<p class="footer">Copyright (c) 2007-2025, NIPPON TELEGRAPH AND TELEPHONE CORPORATION</p>

<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
<script type="text/javascript">
try {
var pageTracker = _gat._getTracker("UA-10244036-1");
pageTracker._trackPageview();
} catch(err) {}</script>
</body>
</html>