Hash: SHA1

>> Um, can't we just get that from pg_settings?
>> Anyway, I'll be deriving settings from the .conf file, since most of the
>> time the Configurator will be run on a new installation.
> Aren't most of the settings all kept in the SHOW variables anyway?

As I said, it may not be applicable to this project, but thought I would
offer. One gotcha the module makes transparent is that in older versions of
PG, the variables are returned in a different way (via RAISE). My module
will allow you to get the configuration for any connected database, for
any configuration file, and the defaults for any known version, and do
quick comparisons between them all. So you could use it to see what has
changed between a particular server and its conf file, or the differences
between two conf files, or the differences between two databases, or even show
what has changed in the default conf file from 7.4.7 and 8.0.1. It will also
allow you to rewrite the conf files in a standard way.

I'm hoping to roll this into 1.44 or 1.45 or DBD::Pg.

- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x14964AC8 200506212046


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not

Reply via email to