| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: InvalidXLogRecPtr in docs |
| Date: | 2010-06-15 05:41:10 |
| Message-ID: | 4C171276.7060207@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15/06/10 08:23, Fujii Masao wrote:
> On Thu, Jun 10, 2010 at 11:06 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'm not sure if it's worth the trouble, or even a particularly smart
>> idea, to force the output of the status function to be monotonic
>> regardless of what happens underneath. I think removing that claim
>> from the docs altogether is the easiest answer.
>
> We should
>
> (1) just remove "While streaming replication is in progress this will
> increase monotonically." from the description about
> pg_last_xlog_receive_location()?
>
> or
>
> (2) add "But if streaming replication is restarted this will back off
> to the beginning of current WAL file" into there?
>
> I'm for (2) since it's more informative. Thought?
Something like (2) seems better, because even if we remove the note that
it increases monotonically, people might still assume that.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2010-06-15 06:05:30 | Re: GUC category cleanup |
| Previous Message | Fujii Masao | 2010-06-15 05:23:32 | Re: InvalidXLogRecPtr in docs |