On Mon, 7 Oct 2019 at 13:17, Christopher Browne <cbbrowne at gmail.com> wrote:

> The way I'd be inclined to adopt it would be as follows...
>
> -  slon should check to see if lock_timeout is available (looking in
> pg_catalog.pg_settings where name='lock_timeout')'
>    - this is probably mostly localized to the function logswitch_finish()
> -  if not, then stay with the current NOWAIT behaviour
> -  if available, then set lock_timeout and attempt without NOWAIT
>    - open question: what's the apropos lock_timeout time?  Probably
> configurable, perhaps that points to a new config parameter to add to
> confoptions.h and confoptions.c
>
> It doesn't seem like either an enormous change or an awfully risky one.
>

It's *somewhat* worse than that; setting lock_timeout to a low-ish value
would risk letting other activities timeout, so we'd only want want the
timeout shortened for this query.  Definitely more fiddly than I was first
thinking.


-- 
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20191010/426b3376/attachment.htm