Taken right straight from my own maintainance notes...

1) what is the syntax for a timestamp entry? If I entered it by hand from the psql
client? Apparently there are a number of valid syntaxes (syntaces?).

2) how large should the timestamp column/attribute be when I create the table by hand?
I'm getting a feeling that internally, the TIMESTAMP datatype is probably
just an array of chars, and consequently, the way you enter it in actually
affects the the size of the piece of data (as opposed to an implicit/understood
size for the datatype because the timestamp data is actually internally the same
thing and the only difference is the way it's represented externally through the
psql client, or the dbish client, or a CGI, or whatever).

3) Where do I go shopping for timestamp formats? I need *one* timestamp that will contain
the date and the time to an accuracy of at least a 10th of a second.

4) found some good documentation at:
http://www.postgresql.org/docs/view.php?version=7.3&idoc=0&file=datatype-datetime.html#DATATYPE-DATETIME-INPUT

5) they say that the format for a timestamp is "timestamp [ (p) ]". is "p" the number of
characters in the timestamp string?

6) w3c got conspicuously funky with their choice of direct objects when they said that
their document at:

http://www.w3.org/TR/NOTE-datetime

... defined a "profile" of ISO 8601. Postgresql claims to be 8601 compliant. If I threw
something like

YYYY-MM-DDThh:mm:ss.sTZD (eg 1997-07-16T19:20:30.45+01:00)

...at postgresql, would it complain? In other words, as
long as I defined the size of the datatype correctly, would that be an acceptable format?

apologies for the non-linear/repetitive thought... I was kind of thinking out loud when I wrote that. Any suggestions for further reading, especially about how to do that with DBI::Pg would be welcome.