> > > I think you misread Mason's post of 20:23 GMT-6 where he says the > created_at values are the *same*, not different. Mason's previous bug > report 3724 also had duplicate rows with matching created_at values. >
Yes, to confirm, the created_at values are the same. The *only* values that are different are updated_at and that value is set via trigger. Another data point that may or may not be relevant: I've been working to set up a warm standby server and have run into some weird behavior there as well. The symptom is the server encounters an error during the file restore, then pre-maturely exits recovery mode. I'm using the pg_standby program for the restore_command in my recovery.conf on the standby server. The error message from the standby server was: Last week I had turned my attention away from the database restore, and didn't notice that our standby server had exited recovery mode on 12/20. Here's the last few lines from the log file (full log attached). 2007-12-20 04:11:43 CST () LOG: restored log file "000000010000042200000057" from archive 2007-12-20 04:13:09 CST () LOG: restored log file "000000010000042200000058" from archive 2007-12-20 04:14:40 CST () LOG: restored log file "000000010000042200000059" from archive 2007-12-20 04:14:40 CST () LOG: invalid info bits 0001 in log file 1058, segment 89, offset 0 2007-12-20 04:14:40 CST () LOG: redo done at 422/58FFEE38 2007-12-20 04:14:40 CST () LOG: restored log file "000000010000042200000058" from archive 2007-12-20 04:14:40 CST () LOG: archive recovery complete 2007-12-20 04:24:57 CST () LOG: database system is ready thanks, Mason
