| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)oss(dot)ntt(dot)co(dot)jp>, "masao(dot)fujii" <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [REVIEW] pg_last_xact_insert_timestamp |
| Date: | 2011-09-30 19:57:19 |
| Message-ID: | CA+TgmoZ9xoagPZpbMi6XCo_a2WyPsNLf8BNFktXb+abKCxHVyg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 30, 2011 at 3:22 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> If the feature could not be done another way, easily, I might agree.
I don't see that you've offered a reasonable alternative. The
alternative proposals that you proposed don't appear to me to be
solving the same problem. AIUI, the requested feature is to be able
to get, on the master, the timestamp of the last commit or abort, just
as we can already get the timestamp of the last commit or abort
replayed on the standby. Nothing you WAL log and no messages you send
to the standby are going to accomplish that goal.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-09-30 20:07:58 | Re: [REVIEW] pg_last_xact_insert_timestamp |
| Previous Message | Simon Riggs | 2011-09-30 19:22:24 | Re: [REVIEW] pg_last_xact_insert_timestamp |