File: set.l.html

package info (click to toggle)
mpsql 2.0-2
  • links: PTS
  • area: non-free
  • in suites: slink
  • size: 2,912 kB
  • ctags: 5,665
  • sloc: ansic: 34,322; makefile: 3,525; sh: 17
file content (111 lines) | stat: -rw-r--r-- 3,901 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
<!-- manual page source format generated by PolyglotMan v3.0.4, -->
<!-- available via anonymous ftp from ftp.cs.berkeley.edu:/ucb/people/phelps/tcltk/rman.tar.Z -->

<HTML>
<HEAD>
<TITLE>SET(SQL) manual page</TITLE>
</HEAD>
<BODY>
<A HREF="sql.html">SQL Reference Contents</A>
 
<H2><A NAME="sect0" HREF="#toc0">NAME </A></H2>
set - set run-time parameters for session  
<H2><A NAME="sect1" HREF="#toc1">SYNOPSIS </A></H2>
<B>set </B> variable 
<B>to </B> 'value1[,value2 ...]' <BR>
  
<H2><A NAME="sect2" HREF="#toc2">DESCRIPTION </A></H2>
<B>Set</B> will modify configuration parameters 
for <I>variable</I> during a session. <P>
Current values can be obtained using <I><A HREF="show.l.html">show</I>(l)</A>
, 
and values can be restored to the defaults using <I><A HREF="reset.l.html">reset</I>(l)</A>
. Parameters and 
values are case-insensitive. Note that the value field is always specified 
as a string, so is enclosed in single-quotes. <P>
<I>DateStyle</I> determines the output 
format for the date and time data types. See <I><A HREF="pgbuiltin.3.html">pgbuiltin</I>(3)</A>
 for more information 
on available styles. <P>
  <CENTER><B>DateStyle Values </B> </CENTER> <P>
 <P>
  <tt> </tt><tt> </tt>ISO<tt> </tt><tt> </tt>- use ISO 8601-style dates 
and times <BR>
 <tt> </tt><tt> </tt>SQL<tt> </tt><tt> </tt>- use Oracle/Ingres-style dates and times <BR>
 <tt> </tt><tt> </tt>Postgres<tt> </tt><tt> </tt>- use traditional 
Postgres format <BR>
 <tt> </tt><tt> </tt>European<tt> </tt><tt> </tt>- use dd/mm/yyyy for numeric date representations. 
<BR>
 <tt> </tt><tt> </tt>NonEuropean<tt> </tt><tt> </tt>- use mm/dd/yyyy for numeric date representations. <BR>
 <tt> </tt><tt> </tt>US<tt> </tt><tt> </tt>- same 
as 'NonEuropean' <BR>
 <tt> </tt><tt> </tt>default<tt> </tt><tt> </tt>- restores the default values ('US,Postgres') <BR>
 <P>
<I>GEQO</I> 
enables or disables the genetic optimizer algorithm. This algorithm is 
<I>on</I> by default, which used GEQO for statements of eight or more tables. 
See the GEQO README for more information. <P>
  <CENTER><B>GEQO Values </B> </CENTER> <P>
 <P>
  <tt> </tt><tt> </tt>on<tt> </tt><tt> </tt>- use for 
statements with 8 or more tables <BR>
 <tt> </tt><tt> </tt>on=10<tt> </tt><tt> </tt>- use for statements with 10 or 
more tables <BR>
 <tt> </tt><tt> </tt>off<tt> </tt><tt> </tt>- do not use the genetic optimizer <BR>
 <P>
<I>R_PLANS</I> enables or 
disables right-hand evaluation of plans. It may be useful when joining big 
relations with small ones. This algorithm is <I>off</I> by default. It's not used 
by GEQO anyway. <P>
 <P>
   <CENTER><B>R_PLANS Values </B> <BR>
 </CENTER> <P>
 <tt> </tt><tt> </tt>on<tt> </tt><tt> </tt>- turn right-hand plan evaluation 
'on' <BR>
 <tt> </tt><tt> </tt>off<tt> </tt><tt> </tt>- do not use right-hand plan evaluation <BR>
 <P>
  
<H2><A NAME="sect3" HREF="#toc3">EXAMPLES </A></H2>
-- <BR>
 --Set the style 
of date to ISO <BR>
 -- <BR>
 set DateStyle to 'ISO' <BR>
 <P>
-- <BR>
 --Set the style of date to SQL 
with European conventions <BR>
 -- <BR>
 set DateStyle to 'SQL,European' <BR>
 <P>
-- <BR>
 --Use GEQO 
for statements with 4 or more tables <BR>
 -- <BR>
 set GEQO to 'on=4' <BR>
 -- <BR>
 --Turn off the 
genetic optimizer <BR>
 -- <BR>
 set GEQO to 'off' <BR>
  
<H2><A NAME="sect4" HREF="#toc4">SEE ALSO </A></H2>
<A HREF="pgbuiltin.3.html">pgbuiltin(3)</A>
, <A HREF="reset.l.html">reset(l)</A>
, 
<A HREF="show.l.html">show(l)</A>
.  
<H2><A NAME="sect5" HREF="#toc5">BUGS </A></H2>
Of course. <P>

<HR><P>
<A NAME="toc"><B>Table of Contents</B></A><P>
<UL>
<LI><A NAME="toc0" HREF="#sect0">NAME</A></LI>
<LI><A NAME="toc1" HREF="#sect1">SYNOPSIS</A></LI>
<LI><A NAME="toc2" HREF="#sect2">DESCRIPTION</A></LI>
<LI><A NAME="toc3" HREF="#sect3">EXAMPLES</A></LI>
<LI><A NAME="toc4" HREF="#sect4">SEE ALSO</A></LI>
<LI><A NAME="toc5" HREF="#sect5">BUGS</A></LI>
</UL>
</BODY></HTML>