| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: InvalidXLogRecPtr in docs |
| Date: | 2010-06-10 01:54:25 |
| Message-ID: | AANLkTimmFy_WMoWoZNHfg8i5ghq3g2XrwmXV_1Krwcn4@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 9, 2010 at 9:46 PM, Takahiro Itagaki
<itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> wrote:
> I found a term "InvalidXLogRecPtr" in 9.0 docs.
> http://developer.postgresql.org/pgdocs/postgres/functions-admin.html#FUNCTIONS-RECOVERY-INFO-TABLE
> | ... then the return value will be InvalidXLogRecPtr (0/0).
>
> I think it should not appear in docs because it's a name for an internal
> constant variable. I'd like to rewrite the description like:
>
> ... then the return value will be 0/0, that is never used in normal cases.
>
> Comments?
Maybe we should be returning NULL instead of 0/0.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2010-06-10 02:07:47 | Re: failover vs. read only queries |
| Previous Message | Robert Haas | 2010-06-10 01:51:39 | Re: Large (almost 50%!) performance drop after upgrading to 8.4.4? |