Skip site navigation (1) Skip section navigation (2)

Re: Eurodates by default

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Yury Bokhoncovich <byg(at)center-f1(dot)ru>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Eurodates by default
Date: 2002-03-20 14:44:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Yury Bokhoncovich <byg(at)center-f1(dot)ru> writes:
> Anyway this closely resembles what with-maxbackends does:
> 1) if you have not specify with-maxbackends number, Pg will have some
> reasonable defaults (compile time, yes?)
> 2) you can change this value at run time (-N option or var in conf file)

> Are you planning to delete that option too?;)

A poor choice of example, because in fact I am planning to delete it ;-).
There's no need for it anymore, because there's no longer any compile-
time limit on MaxBackends.  In general we'd like to move away from
compile-time feature settings, except for cases like SSL or Kerberos
support where the feature depends on software you may not have.

I don't really see why you think it's preferable to use an extra
configure switch than to set a variable in postgresql.conf.

			regards, tom lane

In response to

pgsql-patches by date

Next:From: Thomas LockhartDate: 2002-03-20 15:00:10
Subject: Re: useless statements in parse_datestyle_internal
Previous:From: Yury BokhoncovichDate: 2002-03-20 12:33:12
Subject: useless statements in parse_datestyle_internal

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group