I am trying to figure out what day some things were entered into the
DB. Is there a way to do that?

--Bryan


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

On Fri, Jan 09, 2004 at 11:45:17 -0800,
Bryan Irvine <bryan.irvine (AT) kingcountyjournal (DOT) com> wrote:
Rows do not have timestamps associated with them. You might be able to make
some guesses using your logfile. If this is something you want for the
future you can add a timestamp field to your table and use a trigger to
keep it up to date.

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

On Fri, Jan 09, 2004 at 12:25:45 -0800,
Bryan Irvine <bryan.irvine (AT) kingcountyjournal (DOT) com> wrote:
I don't think there is an FAQ, but it has been discussed on the lists a
few times. You probably want to use a before trigger to set the timestamp
column to current_timestamp on inserts or updates.

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

uhm, *digs toe into ground* where would my logfile be?


---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org

On Fri, Jan 09, 2004 at 13:12:12 -0800,
Bryan Irvine <bryan.irvine (AT) kingcountyjournal (DOT) com> wrote:
The logs might just be being thrown away. They might be being stored using
syslog in which case they would probably be in var/log somewhere. They
might be being saved into a file. Look at the commands used to start
the database server in this case to see where the file is.
For my use I save the logs using multilog, but I don't think any
distributor sets up postgres that way.

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

On Friday 09 January 2004 12:52 pm, Bruno Wolff III wrote:
Creating a timestamp on inserts (not updates) is easy:

create table foo (....., mytimestamp timestamptz not null default
now(), ...);

Cheers,
Steve


---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match