Re: Resolving pg_standby -l - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Resolving pg_standby -l
Date
Msg-id 4A4368F0.5030805@enterprisedb.com
Whole thread Raw
In response to Resolving pg_standby -l  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs wrote:
> Short patch to 
> 1. disable pg_standby -l
>     One line change only appropriate for this stage of release
> 2. Remove mention of -l and link from docs
> 
> pg_standby -l is still accepted, just does nothing (for now).
> 
> Existing code maintained in case we backpatch a fix for linking problem
> at a later date.

Ah, I had forgotten about this already.

Committed. The patch looks very safe to me, but given that we're just
about to wrap the release I'm keeping my fingers crossed that this
didn't break anything,.

I didn't commit this to the back-branches yet, because I'm not sure if
we have consensus on that. If symlinking has a meaningful performance
advantage, someone might be unhappy if we disable that option in a minor
release. I think we should go ahead anyway, but does anyone object?

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Why does pg_standby require libpq.so.5?
Next
From: Fujii Masao
Date:
Subject: Re: Why does pg_standby require libpq.so.5?