1997-04-17 15:50:57 +02:00
|
|
|
/*
|
1997-10-30 17:52:11 +01:00
|
|
|
* Routines for handling of 'SET var TO',
|
|
|
|
* 'SHOW var' and 'RESET var' statements.
|
1997-04-17 15:50:57 +02:00
|
|
|
*
|
1997-11-21 19:12:58 +01:00
|
|
|
* $Id: variable.c,v 1.23 1997/11/21 18:11:20 momjian Exp $
|
1997-04-17 15:50:57 +02:00
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
#include <stdio.h>
|
1997-04-17 15:50:57 +02:00
|
|
|
#include <string.h>
|
1997-06-20 19:17:03 +02:00
|
|
|
#include <ctype.h>
|
1997-11-21 19:12:58 +01:00
|
|
|
#include <time.h>
|
1997-03-25 10:44:00 +01:00
|
|
|
#include "postgres.h"
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
#include "miscadmin.h"
|
1997-03-25 10:44:00 +01:00
|
|
|
#include "tcop/variable.h"
|
1997-04-24 17:41:37 +02:00
|
|
|
#include "utils/builtins.h"
|
|
|
|
#include "optimizer/internal.h"
|
|
|
|
|
1997-09-08 04:41:22 +02:00
|
|
|
extern Cost _cpu_page_wight_;
|
|
|
|
extern Cost _cpu_index_page_wight_;
|
|
|
|
extern bool _use_geqo_;
|
|
|
|
extern int32 _use_geqo_rels_;
|
|
|
|
extern bool _use_right_sided_plans_;
|
1997-03-25 10:44:00 +01:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
/*-----------------------------------------------------------------------*/
|
|
|
|
#if USE_EURODATES
|
1997-09-07 07:04:48 +02:00
|
|
|
#define DATE_EURO TRUE
|
1997-04-17 15:50:57 +02:00
|
|
|
#else
|
|
|
|
#define DATE_EURO FALSE
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*-----------------------------------------------------------------------*/
|
|
|
|
struct PGVariables PGVariables =
|
1997-09-07 07:04:48 +02:00
|
|
|
{
|
|
|
|
{DATE_EURO, Date_Postgres}
|
|
|
|
};
|
1997-04-17 15:50:57 +02:00
|
|
|
|
|
|
|
/*-----------------------------------------------------------------------*/
|
1997-09-07 07:04:48 +02:00
|
|
|
static const char *
|
|
|
|
get_token(char **tok, char **val, const char *str)
|
1997-06-02 13:00:57 +02:00
|
|
|
{
|
1997-09-08 04:41:22 +02:00
|
|
|
const char *start;
|
|
|
|
int len = 0;
|
1997-09-07 07:04:48 +02:00
|
|
|
|
|
|
|
*tok = NULL;
|
|
|
|
if (val != NULL)
|
|
|
|
*val = NULL;
|
|
|
|
|
|
|
|
if (!(*str))
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
/* skip white spaces */
|
|
|
|
while (isspace(*str))
|
|
|
|
str++;
|
|
|
|
if (*str == ',' || *str == '=')
|
|
|
|
elog(WARN, "Syntax error near (%s): empty setting", str);
|
|
|
|
|
|
|
|
/* end of string? then return NULL */
|
|
|
|
if (!(*str))
|
|
|
|
return NULL;
|
|
|
|
|
|
|
|
/* OK, at beginning of non-NULL string... */
|
|
|
|
start = str;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* count chars in token until we hit white space or comma or '=' or
|
|
|
|
* end of string
|
|
|
|
*/
|
|
|
|
while (*str && (!isspace(*str))
|
|
|
|
&& *str != ',' && *str != '=')
|
|
|
|
{
|
|
|
|
str++;
|
|
|
|
len++;
|
|
|
|
}
|
|
|
|
|
|
|
|
*tok = (char *) PALLOC(len + 1);
|
1997-10-25 03:10:58 +02:00
|
|
|
StrNCpy(*tok, start, len+1);
|
1997-09-07 07:04:48 +02:00
|
|
|
|
|
|
|
/* skip white spaces */
|
|
|
|
while (isspace(*str))
|
|
|
|
str++;
|
|
|
|
|
|
|
|
/* end of string? */
|
|
|
|
if (!(*str))
|
|
|
|
{
|
|
|
|
return (str);
|
|
|
|
|
|
|
|
/* delimiter? */
|
|
|
|
}
|
|
|
|
else if (*str == ',')
|
|
|
|
{
|
|
|
|
return (++str);
|
|
|
|
|
|
|
|
}
|
|
|
|
else if ((val == NULL) || (*str != '='))
|
|
|
|
{
|
|
|
|
elog(WARN, "Syntax error near (%s)", str);
|
|
|
|
};
|
|
|
|
|
|
|
|
str++; /* '=': get value */
|
|
|
|
len = 0;
|
|
|
|
|
|
|
|
/* skip white spaces */
|
|
|
|
while (isspace(*str))
|
|
|
|
str++;
|
|
|
|
|
|
|
|
if (*str == ',' || !(*str))
|
|
|
|
elog(WARN, "Syntax error near (=%s)", str);
|
|
|
|
|
|
|
|
start = str;
|
|
|
|
|
|
|
|
/*
|
|
|
|
* count chars in token's value until we hit white space or comma or
|
|
|
|
* end of string
|
|
|
|
*/
|
|
|
|
while (*str && (!isspace(*str)) && *str != ',')
|
|
|
|
{
|
|
|
|
str++;
|
|
|
|
len++;
|
|
|
|
}
|
|
|
|
|
|
|
|
*val = (char *) PALLOC(len + 1);
|
1997-10-25 03:10:58 +02:00
|
|
|
StrNCpy(*val, start, len+1);
|
1997-09-07 07:04:48 +02:00
|
|
|
|
|
|
|
/* skip white spaces */
|
|
|
|
while (isspace(*str))
|
|
|
|
str++;
|
|
|
|
|
|
|
|
if (!(*str))
|
|
|
|
return (NULL);
|
|
|
|
if (*str == ',')
|
|
|
|
return (++str);
|
|
|
|
|
1997-06-02 13:00:57 +02:00
|
|
|
elog(WARN, "Syntax error near (%s)", str);
|
1997-09-07 07:04:48 +02:00
|
|
|
|
|
|
|
return str;
|
1997-06-02 13:00:57 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
/*-----------------------------------------------------------------------*/
|
1997-10-30 17:52:11 +01:00
|
|
|
#if FALSE
|
1997-09-07 07:04:48 +02:00
|
|
|
static bool
|
|
|
|
parse_null(const char *value)
|
|
|
|
{
|
1997-04-17 15:50:57 +02:00
|
|
|
return TRUE;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
static bool
|
|
|
|
show_null(const char *value)
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
return TRUE;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
static bool
|
|
|
|
reset_null(const char *value)
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
return TRUE;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
1997-10-30 17:52:11 +01:00
|
|
|
#endif
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
parse_geqo(const char *value)
|
1997-04-29 06:38:58 +02:00
|
|
|
{
|
1997-09-08 04:41:22 +02:00
|
|
|
const char *rest;
|
|
|
|
char *tok,
|
|
|
|
*val;
|
1997-09-07 07:04:48 +02:00
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
if (value == NULL)
|
|
|
|
{
|
|
|
|
reset_geqo();
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
rest = get_token(&tok, &val, value);
|
|
|
|
if (tok == NULL)
|
|
|
|
elog(WARN, "Value undefined");
|
|
|
|
|
|
|
|
if ((rest) && (*rest != '\0'))
|
|
|
|
elog(WARN, "Unable to parse '%s'", value);
|
|
|
|
|
|
|
|
if (strcasecmp(tok, "on") == 0)
|
|
|
|
{
|
1997-09-08 04:41:22 +02:00
|
|
|
int32 geqo_rels = GEQO_RELS;
|
1997-09-07 07:04:48 +02:00
|
|
|
|
|
|
|
if (val != NULL)
|
|
|
|
{
|
|
|
|
geqo_rels = pg_atoi(val, sizeof(int32), '\0');
|
|
|
|
if (geqo_rels <= 1)
|
|
|
|
elog(WARN, "Bad value for # of relations (%s)", val);
|
|
|
|
PFREE(val);
|
|
|
|
}
|
|
|
|
_use_geqo_ = true;
|
|
|
|
_use_geqo_rels_ = geqo_rels;
|
|
|
|
}
|
|
|
|
else if (strcasecmp(tok, "off") == 0)
|
|
|
|
{
|
|
|
|
if ((val != NULL) && (*val != '\0'))
|
|
|
|
elog(WARN, "%s does not allow a parameter", tok);
|
|
|
|
_use_geqo_ = false;
|
|
|
|
}
|
|
|
|
else
|
|
|
|
elog(WARN, "Bad value for GEQO (%s)", value);
|
|
|
|
|
|
|
|
PFREE(tok);
|
|
|
|
return TRUE;
|
1997-04-29 06:38:58 +02:00
|
|
|
}
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
show_geqo()
|
1997-04-29 06:38:58 +02:00
|
|
|
{
|
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
if (_use_geqo_)
|
|
|
|
elog(NOTICE, "GEQO is ON beginning with %d relations", _use_geqo_rels_);
|
|
|
|
else
|
|
|
|
elog(NOTICE, "GEQO is OFF");
|
|
|
|
return TRUE;
|
1997-04-29 06:38:58 +02:00
|
|
|
}
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
|
|
|
reset_geqo(void)
|
1997-04-29 06:38:58 +02:00
|
|
|
{
|
|
|
|
|
|
|
|
#ifdef GEQO
|
1997-09-07 07:04:48 +02:00
|
|
|
_use_geqo_ = true;
|
1997-04-29 06:38:58 +02:00
|
|
|
#else
|
1997-09-07 07:04:48 +02:00
|
|
|
_use_geqo_ = false;
|
1997-04-29 06:38:58 +02:00
|
|
|
#endif
|
1997-09-07 07:04:48 +02:00
|
|
|
_use_geqo_rels_ = GEQO_RELS;
|
|
|
|
return TRUE;
|
1997-04-29 06:38:58 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
parse_r_plans(const char *value)
|
1997-05-20 12:31:42 +02:00
|
|
|
{
|
1997-11-07 07:43:16 +01:00
|
|
|
if (value == NULL)
|
|
|
|
{
|
|
|
|
reset_r_plans();
|
|
|
|
return TRUE;
|
|
|
|
}
|
1997-05-20 12:31:42 +02:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
if (strcasecmp(value, "on") == 0)
|
|
|
|
_use_right_sided_plans_ = true;
|
|
|
|
else if (strcasecmp(value, "off") == 0)
|
|
|
|
_use_right_sided_plans_ = false;
|
|
|
|
else
|
|
|
|
elog(WARN, "Bad value for Right-sided Plans (%s)", value);
|
|
|
|
|
|
|
|
return TRUE;
|
1997-05-20 12:31:42 +02:00
|
|
|
}
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
show_r_plans()
|
1997-05-20 12:31:42 +02:00
|
|
|
{
|
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
if (_use_right_sided_plans_)
|
|
|
|
elog(NOTICE, "Right-sided Plans are ON");
|
|
|
|
else
|
|
|
|
elog(NOTICE, "Right-sided Plans are OFF");
|
|
|
|
return TRUE;
|
1997-05-20 12:31:42 +02:00
|
|
|
}
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
reset_r_plans()
|
1997-05-20 12:31:42 +02:00
|
|
|
{
|
|
|
|
|
|
|
|
#ifdef USE_RIGHT_SIDED_PLANS
|
1997-09-07 07:04:48 +02:00
|
|
|
_use_right_sided_plans_ = true;
|
1997-05-20 12:31:42 +02:00
|
|
|
#else
|
1997-09-07 07:04:48 +02:00
|
|
|
_use_right_sided_plans_ = false;
|
1997-05-20 12:31:42 +02:00
|
|
|
#endif
|
1997-09-07 07:04:48 +02:00
|
|
|
return TRUE;
|
1997-05-20 12:31:42 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
parse_cost_heap(const char *value)
|
1997-04-24 17:41:37 +02:00
|
|
|
{
|
1997-11-07 07:43:16 +01:00
|
|
|
float32 res;
|
|
|
|
|
|
|
|
if (value == NULL)
|
|
|
|
{
|
|
|
|
reset_cost_heap();
|
|
|
|
return TRUE;
|
|
|
|
}
|
1997-09-07 07:04:48 +02:00
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
res = float4in((char *) value);
|
1997-09-07 07:04:48 +02:00
|
|
|
_cpu_page_wight_ = *res;
|
|
|
|
|
|
|
|
return TRUE;
|
1997-04-24 17:41:37 +02:00
|
|
|
}
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
show_cost_heap()
|
1997-04-24 17:41:37 +02:00
|
|
|
{
|
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
elog(NOTICE, "COST_HEAP is %f", _cpu_page_wight_);
|
|
|
|
return TRUE;
|
1997-04-24 17:41:37 +02:00
|
|
|
}
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
reset_cost_heap()
|
1997-04-24 17:41:37 +02:00
|
|
|
{
|
1997-09-07 07:04:48 +02:00
|
|
|
_cpu_page_wight_ = _CPU_PAGE_WEIGHT_;
|
|
|
|
return TRUE;
|
1997-04-24 17:41:37 +02:00
|
|
|
}
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
parse_cost_index(const char *value)
|
1997-04-24 17:41:37 +02:00
|
|
|
{
|
1997-11-07 07:43:16 +01:00
|
|
|
float32 res;
|
1997-09-07 07:04:48 +02:00
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
if (value == NULL)
|
|
|
|
{
|
|
|
|
reset_cost_index();
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
|
|
|
res = float4in((char *) value);
|
1997-09-07 07:04:48 +02:00
|
|
|
_cpu_index_page_wight_ = *res;
|
|
|
|
|
|
|
|
return TRUE;
|
1997-04-24 17:41:37 +02:00
|
|
|
}
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
show_cost_index()
|
1997-04-24 17:41:37 +02:00
|
|
|
{
|
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
elog(NOTICE, "COST_INDEX is %f", _cpu_index_page_wight_);
|
|
|
|
return TRUE;
|
1997-04-24 17:41:37 +02:00
|
|
|
}
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
reset_cost_index()
|
1997-04-24 17:41:37 +02:00
|
|
|
{
|
1997-09-07 07:04:48 +02:00
|
|
|
_cpu_index_page_wight_ = _CPU_INDEX_PAGE_WEIGHT_;
|
|
|
|
return TRUE;
|
1997-04-24 17:41:37 +02:00
|
|
|
}
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
parse_date(const char *value)
|
1997-06-02 13:00:57 +02:00
|
|
|
{
|
1997-09-08 04:41:22 +02:00
|
|
|
char *tok;
|
|
|
|
int dcnt = 0,
|
|
|
|
ecnt = 0;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
if (value == NULL)
|
|
|
|
{
|
|
|
|
reset_date();
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
while ((value = get_token(&tok, NULL, value)) != 0)
|
1997-06-02 13:00:57 +02:00
|
|
|
{
|
1997-04-17 15:50:57 +02:00
|
|
|
/* Ugh. Somebody ought to write a table driven version -- mjl */
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
if (!strcasecmp(tok, "iso"))
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
DateStyle = USE_ISO_DATES;
|
1997-04-17 15:50:57 +02:00
|
|
|
dcnt++;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
|
|
|
else if (!strcasecmp(tok, "sql"))
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
DateStyle = USE_SQL_DATES;
|
1997-04-17 15:50:57 +02:00
|
|
|
dcnt++;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
|
|
|
else if (!strcasecmp(tok, "postgres"))
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
DateStyle = USE_POSTGRES_DATES;
|
1997-04-17 15:50:57 +02:00
|
|
|
dcnt++;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
|
|
|
else if (!strncasecmp(tok, "euro", 4))
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
EuroDates = TRUE;
|
|
|
|
ecnt++;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
|
|
|
else if ((!strcasecmp(tok, "us"))
|
|
|
|
|| (!strncasecmp(tok, "noneuro", 7)))
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
EuroDates = FALSE;
|
1997-04-17 15:50:57 +02:00
|
|
|
ecnt++;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
|
|
|
else if (!strcasecmp(tok, "default"))
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
DateStyle = USE_POSTGRES_DATES;
|
|
|
|
EuroDates = FALSE;
|
1997-04-17 15:50:57 +02:00
|
|
|
ecnt++;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
1997-04-17 15:50:57 +02:00
|
|
|
else
|
1997-09-07 07:04:48 +02:00
|
|
|
{
|
1997-05-16 09:24:13 +02:00
|
|
|
elog(WARN, "Bad value for date style (%s)", tok);
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
PFREE(tok);
|
1997-06-02 13:00:57 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
if (dcnt > 1 || ecnt > 1)
|
1997-04-17 15:50:57 +02:00
|
|
|
elog(NOTICE, "Conflicting settings for date");
|
1997-06-02 13:00:57 +02:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
return TRUE;
|
1997-06-02 13:00:57 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
show_date()
|
|
|
|
{
|
1997-09-08 04:41:22 +02:00
|
|
|
char buf[64];
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
strcpy(buf, "DateStyle is ");
|
|
|
|
switch (DateStyle)
|
|
|
|
{
|
1997-09-08 04:41:22 +02:00
|
|
|
case USE_ISO_DATES:
|
|
|
|
strcat(buf, "ISO");
|
|
|
|
break;
|
|
|
|
case USE_SQL_DATES:
|
|
|
|
strcat(buf, "SQL");
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
strcat(buf, "Postgres");
|
|
|
|
break;
|
1997-05-16 09:24:13 +02:00
|
|
|
};
|
1997-09-07 07:04:48 +02:00
|
|
|
strcat(buf, " with ");
|
|
|
|
strcat(buf, ((EuroDates) ? "European" : "US (NonEuropean)"));
|
|
|
|
strcat(buf, " conventions");
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
|
|
|
|
elog(NOTICE, buf, NULL);
|
|
|
|
|
|
|
|
return TRUE;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-09-07 07:04:48 +02:00
|
|
|
reset_date()
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
DateStyle = USE_POSTGRES_DATES;
|
|
|
|
EuroDates = FALSE;
|
|
|
|
|
|
|
|
return TRUE;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-11-10 16:24:56 +01:00
|
|
|
/* Timezone support
|
|
|
|
* Working storage for strings is allocated with an arbitrary size of 64 bytes.
|
|
|
|
*/
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
static char *defaultTZ = NULL;
|
1997-11-10 16:24:56 +01:00
|
|
|
static char TZvalue[64];
|
|
|
|
static char tzbuf[64];
|
1997-11-07 07:43:16 +01:00
|
|
|
|
1997-11-10 16:37:15 +01:00
|
|
|
/* parse_timezone()
|
|
|
|
* Handle SET TIME ZONE...
|
|
|
|
* Try to save existing TZ environment variable for later use in RESET TIME ZONE.
|
|
|
|
* - thomas 1997-11-10
|
|
|
|
*/
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-10-30 17:52:11 +01:00
|
|
|
parse_timezone(const char *value)
|
|
|
|
{
|
|
|
|
char *tok;
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
if (value == NULL)
|
|
|
|
{
|
|
|
|
reset_timezone();
|
|
|
|
return TRUE;
|
|
|
|
}
|
|
|
|
|
1997-10-30 17:52:11 +01:00
|
|
|
while ((value = get_token(&tok, NULL, value)) != 0)
|
|
|
|
{
|
1997-11-10 16:24:56 +01:00
|
|
|
/* Not yet tried to save original value from environment? */
|
|
|
|
if (defaultTZ == NULL)
|
1997-11-07 07:43:16 +01:00
|
|
|
{
|
1997-11-10 16:24:56 +01:00
|
|
|
/* found something? then save it for later */
|
|
|
|
if (getenv("TZ") != NULL)
|
1997-11-07 07:43:16 +01:00
|
|
|
{
|
1997-11-10 16:24:56 +01:00
|
|
|
defaultTZ = getenv("TZ");
|
|
|
|
if (defaultTZ == NULL)
|
|
|
|
defaultTZ = (char *) -1;
|
|
|
|
else
|
|
|
|
strcpy(TZvalue, defaultTZ);
|
1997-11-07 07:43:16 +01:00
|
|
|
}
|
1997-11-10 16:24:56 +01:00
|
|
|
/* found nothing so mark with an invalid pointer */
|
1997-11-07 07:43:16 +01:00
|
|
|
else
|
|
|
|
{
|
1997-11-10 16:24:56 +01:00
|
|
|
defaultTZ = (char *) -1;
|
1997-11-07 07:43:16 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
1997-11-10 16:24:56 +01:00
|
|
|
strcpy(tzbuf, "TZ=");
|
|
|
|
strcat(tzbuf, tok);
|
|
|
|
if (putenv(tzbuf) != 0)
|
|
|
|
elog(WARN, "Unable to set TZ environment variable to %s", tok);
|
|
|
|
|
1997-10-30 17:52:11 +01:00
|
|
|
tzset();
|
|
|
|
PFREE(tok);
|
|
|
|
}
|
|
|
|
|
|
|
|
return TRUE;
|
|
|
|
} /* parse_timezone() */
|
|
|
|
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-10-30 17:52:11 +01:00
|
|
|
show_timezone()
|
|
|
|
{
|
|
|
|
char *tz;
|
|
|
|
|
|
|
|
tz = getenv("TZ");
|
|
|
|
|
1997-11-10 16:24:56 +01:00
|
|
|
elog(NOTICE, "Time zone is %s", ((tz != NULL)? tz: "unknown"));
|
1997-10-30 17:52:11 +01:00
|
|
|
|
|
|
|
return TRUE;
|
|
|
|
} /* show_timezone() */
|
|
|
|
|
1997-11-10 16:24:56 +01:00
|
|
|
/* reset_timezone()
|
|
|
|
* Set TZ environment variable to original value.
|
|
|
|
* Note that if TZ was originally not set, TZ should be cleared.
|
|
|
|
* unsetenv() works fine, but is BSD, not POSIX, and is not available
|
|
|
|
* under Solaris, among others. Apparently putenv() called as below
|
|
|
|
* clears the process-specific environment variables.
|
|
|
|
* Other reasonable arguments to putenv() (e.g. "TZ=", "TZ", "") result
|
|
|
|
* in a core dump (under Linux anyway).
|
|
|
|
*/
|
1997-11-07 07:43:16 +01:00
|
|
|
bool
|
1997-10-30 17:52:11 +01:00
|
|
|
reset_timezone()
|
|
|
|
{
|
1997-11-07 07:43:16 +01:00
|
|
|
if ((defaultTZ != NULL) && (defaultTZ != (char *) -1))
|
|
|
|
{
|
1997-11-10 16:24:56 +01:00
|
|
|
strcpy(tzbuf, "TZ=");
|
|
|
|
strcat(tzbuf, TZvalue);
|
|
|
|
if (putenv(tzbuf) != 0)
|
|
|
|
elog(WARN, "Unable to set TZ environment variable to %s", TZvalue);
|
1997-11-07 07:43:16 +01:00
|
|
|
}
|
|
|
|
else
|
|
|
|
{
|
1997-11-10 16:24:56 +01:00
|
|
|
strcpy(tzbuf, "=");
|
|
|
|
if (putenv(tzbuf) != 0)
|
|
|
|
elog(WARN, "Unable to clear TZ environment variable", NULL);
|
1997-11-07 07:43:16 +01:00
|
|
|
}
|
1997-10-30 17:52:11 +01:00
|
|
|
tzset();
|
|
|
|
|
|
|
|
return TRUE;
|
|
|
|
} /* reset_timezone() */
|
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
/*-----------------------------------------------------------------------*/
|
|
|
|
struct VariableParsers
|
1997-09-07 07:04:48 +02:00
|
|
|
{
|
1997-09-08 04:41:22 +02:00
|
|
|
const char *name;
|
1997-09-08 23:56:23 +02:00
|
|
|
bool (*parser) (const char *);
|
|
|
|
bool (*show) ();
|
|
|
|
bool (*reset) ();
|
1997-09-08 04:41:22 +02:00
|
|
|
} VariableParsers[] =
|
1997-09-07 07:04:48 +02:00
|
|
|
|
|
|
|
{
|
1997-11-14 16:34:09 +01:00
|
|
|
{ "datestyle", parse_date, show_date, reset_date },
|
|
|
|
{ "timezone", parse_timezone, show_timezone, reset_timezone },
|
|
|
|
{ "cost_heap", parse_cost_heap, show_cost_heap, reset_cost_heap },
|
|
|
|
{ "cost_index", parse_cost_index, show_cost_index, reset_cost_index },
|
|
|
|
{ "geqo", parse_geqo, show_geqo, reset_geqo },
|
|
|
|
{ "r_plans", parse_r_plans, show_r_plans, reset_r_plans },
|
|
|
|
{ NULL, NULL, NULL, NULL }
|
1997-09-07 07:04:48 +02:00
|
|
|
};
|
1997-04-17 15:50:57 +02:00
|
|
|
|
|
|
|
/*-----------------------------------------------------------------------*/
|
1997-09-07 07:04:48 +02:00
|
|
|
bool
|
|
|
|
SetPGVariable(const char *name, const char *value)
|
|
|
|
{
|
1997-04-17 15:50:57 +02:00
|
|
|
struct VariableParsers *vp;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
for (vp = VariableParsers; vp->name; vp++)
|
|
|
|
{
|
|
|
|
if (!strcasecmp(vp->name, name))
|
|
|
|
return (vp->parser) (value);
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
elog(NOTICE, "Unrecognized variable %s", name);
|
1997-04-02 20:24:52 +02:00
|
|
|
|
1997-03-25 10:44:00 +01:00
|
|
|
return TRUE;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
1997-03-25 10:44:00 +01:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
/*-----------------------------------------------------------------------*/
|
1997-09-07 07:04:48 +02:00
|
|
|
bool
|
|
|
|
GetPGVariable(const char *name)
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
struct VariableParsers *vp;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
for (vp = VariableParsers; vp->name; vp++)
|
|
|
|
{
|
|
|
|
if (!strcasecmp(vp->name, name))
|
|
|
|
return (vp->show) ();
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
elog(NOTICE, "Unrecognized variable %s", name);
|
|
|
|
|
|
|
|
return TRUE;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
|
1997-04-17 15:50:57 +02:00
|
|
|
/*-----------------------------------------------------------------------*/
|
1997-09-07 07:04:48 +02:00
|
|
|
bool
|
|
|
|
ResetPGVariable(const char *name)
|
|
|
|
{
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
struct VariableParsers *vp;
|
1997-06-20 19:17:03 +02:00
|
|
|
|
1997-09-07 07:04:48 +02:00
|
|
|
for (vp = VariableParsers; vp->name; vp++)
|
|
|
|
{
|
|
|
|
if (!strcasecmp(vp->name, name))
|
|
|
|
return (vp->reset) ();
|
|
|
|
}
|
1997-06-20 19:17:03 +02:00
|
|
|
|
To: Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
Subject: Re: [PATCHES] SET DateStyle patches
On Tue, 22 Apr 1997, Thomas Lockhart wrote:
> Some more patches! These (try to) finish implementing SET variable TO value
> for "DateStyle" (changed the name from simply "date" to be more descriptive).
> This is based on code from Martin and Bruce (?), which was easy to modify.
> The syntax is
>
> SET DateStyle TO 'iso'
> SET DateStyle TO 'postgres'
> SET DateStyle TO 'sql'
> SET DateStyle TO 'european'
> SET DateStyle TO 'noneuropean'
> SET DateStyle TO 'us' (same as "noneuropean")
> SET DateStyle TO 'default' (current same as "postgres,us")
>
> ("european" is just compared for the first 4 characters, and "noneuropean"
> is compared for the first 7 to allow less typing).
>
> Multiple arguments are allowed, so SET datestyle TO 'sql,euro' is valid.
>
> My mods also try to implement "SHOW variable" and "RESET variable", but
> that part just core dumps at the moment. I would guess that my errors
> are obvious to someone who knows what they are doing with the parser stuff,
> so if someone (Bruce and/or Martin??) could have it do the right thing
> we will have a more complete set of what we need.
>
> Also, I would like to have a floating point precision global variable to
> implement "SET precision TO 10" and perhaps "SET precision TO 10,2" for
> float8 and float4, but I don't know how to do that for integer types rather
> than strings. If someone is fixing the SHOW and RESET code, perhaps they can
> add some hooks for me to do the floats while they are at it.
>
> I've left some remnants of variable structures in the source code which
> I did not use in the interests of getting something working for v6.1.
> We'll have time to clean things up for the next release...
1997-04-23 05:18:27 +02:00
|
|
|
elog(NOTICE, "Unrecognized variable %s", name);
|
|
|
|
|
|
|
|
return TRUE;
|
1997-09-07 07:04:48 +02:00
|
|
|
}
|