From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Bryan Irvine <bryan(dot)irvine(at)kingcountyjournal(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Datestamps |
Date: | 2004-01-09 21:39:25 |
Message-ID: | 20040109213925.GA17189@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Fri, Jan 09, 2004 at 13:12:12 -0800,
Bryan Irvine <bryan(dot)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.
>
> uhm, *digs toe into ground* where would my logfile be?
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruno Wolff III | 2004-01-09 21:41:45 | Re: psql error: could not connect to server |
Previous Message | bartvde | 2004-01-09 21:39:09 | psql error: could not connect to server |