| From: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com> |
| Cc: | Adrien Nayrat <adrien(dot)nayrat(at)dalibo(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Christoph Berg <myon(at)debian(dot)org>, Craig Ringer <craig(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: LSN as a recovery target |
| Date: | 2016-08-20 13:59:26 |
| Message-ID: | d7fb44c6-973d-4783-507d-73e3e1ad8587@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 20/08/2016 15:41, Michael Paquier wrote:
> On Sat, Aug 20, 2016 at 10:44 AM, Petr Jelinek <petr(at)2ndquadrant(dot)com> wrote:
>> If we want to specifically name the recovery_target_lsn in the message, we
>> could probably do it using context.
>
> So that would be basically assigning error_context_stack for each item
> parsed for recovery.conf? That seems a bit narrow as usually
> recovery.conf is not that long..
>
That'd still be an improvement, since the error message doesn't even
mention that the error comes from recovery.conf. I agree it can't come
from many places, but it may be useful for some people.
--
Julien Rouhaud
http://dalibo.com - http://dalibo.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-08-20 14:01:02 | Re: Logical decoding slots can go backwards when used from SQL, docs are wrong |
| Previous Message | Craig Ringer | 2016-08-20 13:49:56 | Re: [PATCH] bigint txids vs 'xid' type, new txid_recent(bigint) => xid |