| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: track_commit_timestamp and COMMIT PREPARED |
| Date: | 2015-09-02 14:14:52 |
| Message-ID: | CAHGQGwFLYW55-eKoapG7LVrTpOj-9ttPer_XLwkOuD7yQoxAWw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 5, 2015 at 2:16 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Mon, Aug 3, 2015 at 10:31 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> track_commit_timestamp tracks COMMIT PREPARED as expected in standby server,
>> but not in master server. Is this intentional? It should track COMMIT PREPARED
>> even in master? Otherwise, we cannot use commit_timestamp feature to check
>> the replication lag properly while we use 2PC.
>
> That sounds like it must be a bug. I think you should add it to the
> open items list.
Yep, added.
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-09-02 14:30:08 | Re: Hooking at standard_join_search (Was: Re: Foreign join pushdown vs EvalPlanQual) |
| Previous Message | Andres Freund | 2015-09-02 14:12:25 | Re: Memory prefetching while sequentially fetching from SortTuple array, tuplestore |