Re: check_recovery_target_lsn() does a PG_CATCH without a throw

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: check_recovery_target_lsn() does a PG_CATCH without a throw
Date: 2019-06-23 17:21:02
Message-ID: 4f15b224-b307-ceed-dda2-7c1b7052c08e@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-06-20 18:05, Andres Freund wrote:
> Hi,
>
> On 2019-06-20 15:42:14 +0200, Peter Eisentraut wrote:
>> On 2019-06-12 13:16, Peter Eisentraut wrote:
>>> I haven't figured out the time zone issue yet, but I guess the solution
>>> might involve moving some of the code from check_recovery_target_time()
>>> to assign_recovery_target_time().
>>
>> I think that won't work either. What we need to do is postpone the
>> interpretation of the timestamp string until after all the GUC
>> processing is done. So check_recovery_target_time() would just do some
>> basic parsing checks, but stores the string. Then when we need the
>> recovery_target_time_value we do the final parsing. Then we can be sure
>> that the time zone is all set.
>
> That sounds right to me.

Updated patch for that.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
v2-0001-Remove-explicit-error-handling-for-obsolete-date-.patch text/plain 14.7 KB
v2-0002-Don-t-call-data-type-input-functions-in-GUC-check.patch text/plain 8.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-06-23 17:25:26 Re: Fix doc bug in logical replication.
Previous Message Justin Pryzby 2019-06-23 14:25:47 Re: make \d pg_toast.foo show its indices ; and, \d toast show its main table ; and \d relkind=I show its partitions (and tablespace)