On Wednesday 08 December 2010 21:58:46 you wrote: > On Thu, Dec 9, 2010 at 1:37 AM, Gabi Julien <gabi.jul...@broadsign.com> wrote: > > slave# /etc/init.d/postgresql start > > slave# psql -hlocalhost my_db -c "select pg_last_xact_replay_timestamp(), > > now() as not_modified_since;" > > pg_last_xact_replay_timestamp | not_modified_since > > -------------------------------+------------------------------- > > | 2010-12-08 16:06:09.920219+00
> We should return the timestamp of last valid checkpoint rather than NULL in > that > case? Well, I think this behavior would be more appreciated by postgresql users in general. The case where the slave can be restarted after a clean shutdown is rare but we need to consider it nonetheless. In my case I implemented a custom function that reads the last returned timestamp from a new file on disk. This is not a perfect solution since the value returned might be older then the actual state of the replication but it's good enough for my needs. Regards, Gabi Julien -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
