hi
got new 9.1, straight from git.
compiled, installed.
did initdb, and then set config values using this script:
perl -pi -e '
s/\A \s* (?: [#] \s* )? listen_addresses \s* = \s*.*/listen_addresses =
\047*\047/x;
s/\A \s* (?: [#] \s* )? log_destination \s* = \s*.*/log_destination =
On 13.04.2011 10:49, hubert depesz lubaczewski wrote:
hi
got new 9.1, straight from git.
compiled, installed.
did initdb, and then set config values using this script:
perl -pi -e '
s/\A \s* (?: [#] \s* )? listen_addresses \s* = \s*.*/listen_addresses =
\047*\047/x;
s/\A \s* (?: [#] \s*
On 13.04.2011 14:18, Heikki Linnakangas wrote:
On 13.04.2011 10:49, hubert depesz lubaczewski wrote:
hi
got new 9.1, straight from git.
compiled, installed.
did initdb, and then set config values using this script:
perl -pi -e '
s/\A \s* (?: [#] \s* )? listen_addresses \s* =
On Wed, Apr 13, 2011 at 8:18 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Yep :-(. I'm thinking we need to revert that change, now that we know there
was a reason for only checking the end-of-WAL when doing archive recovery
after all. We can keep it as a warning, though.
