postgresql-setup: add $PGSETUP_INITDB_OPTIONS

Users may now specify by this variable parameters passed to initdb
run.  See `man initdb(1)`.  This may help if user gets stacked
with bug #1007802.

Related: #1007802
Version: 9.3.2-4
This commit is contained in:
Pavel Raiskup 2014-01-09 09:45:02 +01:00
parent 083dd21498
commit 2f213ebd1d
2 changed files with 5 additions and 2 deletions

View File

@ -80,8 +80,10 @@ perform_initdb(){
fi
# Initialize the database
$SU -l postgres -c "$PGENGINE/initdb --pgdata='$PGDATA' --auth='ident'" \
>> "$PGLOG" 2>&1 < /dev/null
initdbcmd="$PGENGINE/initdb --pgdata='$PGDATA' --auth='ident'"
initdbcmd+=" $PGSETUP_INITDB_OPTIONS"
$SU -l postgres -c "$initdbcmd" >> "$PGLOG" 2>&1 < /dev/null
# Create directory for postmaster log files
mkdir "$PGDATA/pg_log"

View File

@ -1125,6 +1125,7 @@ fi
%changelog
* Mon Jan 13 2014 Pavel Raiskup <praiskup@redhat.com> - 9.3.2-4
- postgresql-setup(upgrade): don't stop old server when it can not be started
- postgresql-setup(initdb, upgrade): add $PGSETUP_INITDB_OPTIONS
* Fri Jan 10 2014 Pavel Raiskup <praiskup@redhat.com> - 9.3.2-3
- build with -O3 on ppc64 (private #1051075)