Re: Resolving pg_standby -l

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Resolving pg_standby -l
Date: 2009-06-25 12:09:20
Message-ID: 4A4368F0.5030805@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2009-06-25 13:03:33 Re: Why does pg_standby require libpq.so.5?
Previous Message Magnus Hagander 2009-06-25 11:33:13 Re: Why does pg_standby require libpq.so.5?