pgsql: Disable pg_standby -l option because the backend doesn't expect - Mailing list pgsql-committers

From heikki@postgresql.org (Heikki Linnakangas)
Subject pgsql: Disable pg_standby -l option because the backend doesn't expect
Date
Msg-id 20090625120311.177D475331E@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Disable pg_standby -l option because the backend doesn't expect the recovered
file to be a symlink. We tried to fix this issue with an earlier server-side
patch, but it didn't fix the whole issue.

The same bug is present in older releases as well, but the 8.4 train is
about to leave the station, and I'm not sure if have consensus on whether
we can remove the -l option in back-branches or do we need to attempt a
server-side fix to make symlinking safe.

Patch by Simon Riggs, per discussion on bug identified by Fujii Masao.

Modified Files:
--------------
    pgsql/contrib/pg_standby:
        pg_standby.c (r1.24 -> r1.25)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_standby/pg_standby.c?r1=1.24&r2=1.25)
    pgsql/doc/src/sgml:
        pgstandby.sgml (r2.9 -> r2.10)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/pgstandby.sgml?r1=2.9&r2=2.10)

pgsql-committers by date:

Previous
From: mha@postgresql.org (Magnus Hagander)
Date:
Subject: pgsql: Disallow empty passwords in LDAP authentication, the same way we
Next
From: devrim@pgfoundry.org (User Devrim)
Date:
Subject: press - pr: HTML fixes