Re: Permanent settings

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 20 Feb 2008 13:55:05 -0500
Aidan Van Dyk <aidan@highrise.ca> wrote:

> Once we have people comfortable with it rewriting the file, the
> bikeshedding can start as to how to "use" it through the SQL
> interface.
> 
> But, until there's code out there...
> <bikeshedding>
>     But as Tom said, that's *really* changing what SET has
> tradionally been.
> 
>     Why is a function something like this not sufficient:
>         pg_save_setting('work_mem', '65MB', 'comment so I
> remeber') or,
>         pg_save_setting('work_mem', '65MB')
>     or even
>         pg_save_setting('work_mem')
> 
>     Since it's a function:
>     1) It's "implementable" by anybody, in any fashion
>     2) It's implemtation is easily replacable by anyone, in any
> fashion 3) It's easily backportable to adminpack/8.3/8.2/8.1 for
> those who want it
> </bikeshedding>

I am not opposed to the above. I was trying to make a point about the
ignorance of the point and drool crowd statement.

Sincerely,

Joshua D. Drake

- -- 
The PostgreSQL Company since 1997: http://www.commandprompt.com/ 
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director |  PostgreSQL political pundit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFHvHkKATb/zqfZUUQRAo2TAJsEGcTKCSaM7klq4KFYtuFT035nAwCfeAIr
KfaC5FrE3jSZ0V10eX8LOME=
=BUPQ
-----END PGP SIGNATURE-----