| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: timestamp of the last replayed transaction |
| Date: | 2010-11-10 01:55:46 |
| Message-ID: | AANLkTinu-aP-avqs7-WFDru0W3oJQhnuqwTJ3OgUTGgE@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 10, 2010 at 3:28 AM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 11/9/10 5:44 AM, Fujii Masao wrote:
>> But, pg_last_xact_replay_timestamp is more intuitive for many people?
>> If so, let's change
>> the name.
>
> *None* of these names are intuitive. So let's just go for consistency.
OK. I changed the name to pg_last_xact_replay_timestamp.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| Attachment | Content-Type | Size |
|---|---|---|
| pg_last_xact_replay_timestamp_v1.patch | application/octet-stream | 3.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-11-10 03:31:39 | Re: Protecting against unexpected zero-pages: proposal |
| Previous Message | Gurjeet Singh | 2010-11-10 00:58:27 | Re: DROP TABLESPACE needs crash-resistance |