Re: Default timezone changes in 9.1

On 2012-12-16, Terence Ferraro <terencejferraro(at)gmail(dot)com> wrote:

> With the exception of a few parameters (max_connections and the ssl related
> variables that we enable), the default configuration file (circa 9.0) has
> worked extremely well across 100+ machines so far over the last two years
> and counting. However, we are simply deploying these on commodity machines
> ($300-400 off the shelf). Spec wise such machines have not changed
> significantly (I suppose the shift away from higher clock speeds to more
> cores can be thanked for that).

You cam possibly get some of what you want using "SQL" like:

alter database "DB_NAME" set timezone = 'localtime';

You can do the similarly with other connection parameters on a
per-user or per-database basis too.

--
⚂⚃ 100% natural