Re: [HACKERS] Exporting PGINTERVALSTYLE prevents access to older server versions

2008-11-25 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > On Tuesday 25 November 2008 16:42:57 Tom Lane wrote: >> ! putenv("PGOPTIONS=--intervalstyle=postgres_verbose"); >> So I guess the real question is what is the >> use case for having pg_regress talk to older servers? > There is no use. I was j

Re: [HACKERS] Exporting PGINTERVALSTYLE prevents access to older server versions

2008-11-25 Thread Peter Eisentraut
On Tuesday 25 November 2008 16:42:57 Tom Lane wrote: > --- 716,722 > */ > putenv("PGTZ=PST8PDT"); > putenv("PGDATESTYLE=Postgres, MDY"); > ! putenv("PGOPTIONS=--intervalstyle=postgres_verbose"); > > if (temp_install) > { > > when it struck me that

Re: [HACKERS] Exporting PGINTERVALSTYLE prevents access to older server versions

2008-11-25 Thread Tom Lane
I wrote: > Peter Eisentraut <[EMAIL PROTECTED]> writes: >> (What is the use case for this variable anyway? Is it there just >> because PGDATESTYLE was there previously?) > Pretty much. I'd be fine with taking it out entirely. Actually ... I started to take this out and replace *** pgsql/src/t

Re: [HACKERS] Exporting PGINTERVALSTYLE prevents access to older server versions

2008-11-25 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Exporting PGINTERVALSTYLE causes errors of the following kind when > connecting to an older server version: > psql: FATAL: unrecognized configuration parameter "intervalstyle" Ooops. > (What is the use case for this variable anyway? Is it there j

[HACKERS] Exporting PGINTERVALSTYLE prevents access to older server versions

2008-11-25 Thread Peter Eisentraut
Exporting PGINTERVALSTYLE causes errors of the following kind when connecting to an older server version: psql: FATAL: unrecognized configuration parameter "intervalstyle" Should the processing of this variable be made conditional upon the server version? (What is the use case for this vari