Bug 978570 - postgresql.conf is not updated
Summary: postgresql.conf is not updated
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: postgresql
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Raiskup
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-26 20:19 UTC by Martí­n Marqués
Modified: 2013-06-27 06:44 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-27 06:44:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Martí­n Marqués 2013-06-26 20:19:35 UTC
Description of problem:

There are old parameters in postgresql.conf, which are not available anymore, so commenting them out will make PostgreSQL not start.

Haven't checked, but I hope there aren't other parameters which were removed, or missing new ones.

Version-Release number of selected component (if applicable):

postgresql-server-9.2.4-1.fc18.x86_64

How reproducible:

Uncomment the option wal_sender_delay in the postgresql.conf file and restart postgresql.

Steps to Reproduce:
1.
2.
3.

Actual results:

wal_sender_delay shouldn't be in the postgresql.conf file.

Expected results:


Additional info:

Comment 1 Pavel Raiskup 2013-06-27 06:44:46 UTC
Martín, thanks for the report.

> There are old parameters in postgresql.conf, which are not available
> anymore, so commenting them out will make PostgreSQL not start.
>
> Haven't checked, but I hope there aren't other parameters which were
> removed, or missing new ones.
>
> Version-Release number of selected component (if applicable):
>
> postgresql-server-9.2.4-1.fc18.x86_64
>
> How reproducible:
>
> Uncomment the option wal_sender_delay in the postgresql.conf file and
> restart postgresql.

I checked the postgresql-server-9.2.4-1.fc18.x86_64 and the
postgresql.conf.sample does not contain the wal_sender_delay parameter.

Probably your postgresql.conf was installed in older fedora and then you made
an upgrade?  If this is the case, the upgrade process is unable to cover this
details.  You are always allowed to check the
/usr/share/pgsql/postgresql.conf.sample file.

If I'm not guessing good, please feel free to reopen, thanks, Pavel


Note You need to log in before you can comment on or make changes to this bug.