Blame SOURCES/postgresql-config-comment.patch

582c4b
Add note warning users that Postgres' port number is forced in the service
582c4b
file, mainly because it's traditional in Red Hat installations to set it
582c4b
there rather than in postgresql.conf.  (There are minor usability benefits
582c4b
to doing it this way though, for example that the postmaster's port number
582c4b
is visible in "ps" as part of its command line.)
582c4b
582c4b
582c4b
diff -Naur postgresql-9.2rc1.orig/src/backend/utils/misc/postgresql.conf.sample postgresql-9.2rc1/src/backend/utils/misc/postgresql.conf.sample
582c4b
--- postgresql-9.2rc1.orig/src/backend/utils/misc/postgresql.conf.sample	2012-08-23 18:06:49.000000000 -0400
582c4b
+++ postgresql-9.2rc1/src/backend/utils/misc/postgresql.conf.sample	2012-09-01 21:57:55.498629897 -0400
582c4b
@@ -61,6 +61,8 @@
582c4b
 					# defaults to 'localhost'; use '*' for all
582c4b
 					# (change requires restart)
582c4b
 #port = 5432				# (change requires restart)
582c4b
+# Note: In RHEL/Fedora installations, you can't set the port number here;
582c4b
+# adjust it in the service file instead.
582c4b
 #max_connections = 100			# (change requires restart)
582c4b
 # Note:  Increasing max_connections costs ~400 bytes of shared memory per
582c4b
 # connection slot, plus lock space (see max_locks_per_transaction).