Excerpts from Daymel Bonne Solís's message of mar nov 08 15:46:24 -0300 2011: > Al cargar el módulo 'pg_stat_statements' y declarar la variable > custom_variable_classes = 'pg_stat_statements' en el postgresql.conf el > servidor lanza el siguiente error tratando de iniciar: > > LOG: unrecognized configuration parameter "custom_variable_classes" in > file "/home/bonne/code/pgsql/install/92_rel/data/postgresql.conf" line 133 > FATAL: configuration file > "/home/bonne/code/pgsql/install/92_rel/data/postgresql.conf" contains errors > > Cambió la forma de definir variables en la versión 9.2??
Sí, ya no existe custom_variable_classes. commit 1a00c0ef5368bb7b8ddcb3cf279df36577918ac4 Author: Tom Lane <[email protected]> Date: Tue Oct 4 12:36:18 2011 -0400 Remove the custom_variable_classes parameter. This variable provides only marginal error-prevention capability (since it can only check the prefix of a qualified GUC name), and the consensus is that that isn't worth the amount of hassle that maintaining the setting creates for DBAs. So, let's just remove it. With this commit, the system will silently accept a value for any qualified GUC name at all, whether it has anything to do with any known extension or not. (Unqualified names still have to match known built-in settings, though; and you will get a WARNING at extension load time if there's an unrecognized setting with that extension's prefix.) There's still some discussion ongoing about whether to tighten that up and if so how; but if we do come up with a solution, it's not likely to look anything like custom_variable_classes. -- Álvaro Herrera <[email protected]> - Enviado a la lista de correo pgsql-es-ayuda ([email protected]) Para cambiar tu suscripci�n: http://www.postgresql.org/mailpref/pgsql-es-ayuda
