- 26 4月, 1997 6 次提交
-
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
do this completely last time and Thomas is creating patches on files that aren't supposed to exist :(
-
由 Marc G. Fournier 提交于
Remove bin/Makefile.global since it wasn't actually *doing* anything that Makefile.global hadn't already done
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
Here are patches which should help fix timezone problems in the datetime and abstime code. Also, I repatched varlena.c to add in some comments and a little error checking on top of Vadim's earlier repairs. There are slight mods to the circle data type to have the distance operator between circles measure the distance between closest points rather than between centers.
-
- 25 4月, 1997 6 次提交
-
-
由 Marc G. Fournier 提交于
Subject: [PATCHES] Patches for compiling 6.1 on Digital Unix 3.2c Attached to this message are the patches I needed to compile 6.1 cleanly under Digital Unix 3.2c with DEC cc. I hope these are the last ones. At least, the number of files needing a patch has decreased noticeably since I sent my previous patches. Nice work :-) One of the patches is a bug fix, but I'm including it here anyway. With these patches applied, the beast seems to work properly. However, I've done only some preliminary tests. More on this later (but hopefully before the April 30 deadline... :-)
-
由 Marc G. Fournier 提交于
postgres backend processes end up as so called zombies. It seems that only Linux a.out (libc.4.6.27) systems are affected. By: Wolfgang Roth <roth@statistik.uni-mannheim.de>
-
由 Marc G. Fournier 提交于
Doug Neuhauser <doug@seismo.berkeley.edu> on April 15th
-
由 Vadim B. Mikheev 提交于
Added #define BTREE_VERSION_1.
-
由 Vadim B. Mikheev 提交于
* npages = index_pages * selectivity_of_1st_attr_clause(s)
-
由 Vadim B. Mikheev 提交于
joininfo (in add_join_clause_info_to_rels()) : clause may be commutted later.
-
- 24 4月, 1997 12 次提交
-
-
由 Vadim B. Mikheev 提交于
nestloop's join clauses doesn't work in some cases: * 1. fix_indxqual_references may change varattno-s in * inner_indxqual; * 2. clauses may be commuted
-
由 Vadim B. Mikheev 提交于
-
由 Vadim B. Mikheev 提交于
-
由 Vadim B. Mikheev 提交于
-
由 Vadim B. Mikheev 提交于
SET cost_heap(cost_index) TO ...
-
由 Vadim B. Mikheev 提交于
#define _CPU_INDEX_PAGE_WEIGHT_: 0.033 --> 0.017
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
tests now let you know if it is ok/failed :)
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
Satoshi Ishikawa <power@sekine.densi.gifu-u.ac.jp>
-
由 Marc G. Fournier 提交于
-
- 23 4月, 1997 12 次提交
-
-
由 Vadim B. Mikheev 提交于
-
由 Vadim B. Mikheev 提交于
-
由 Vadim B. Mikheev 提交于
2. vacuum() call changed (ANALYZE).
-
由 Vadim B. Mikheev 提交于
2. New VACUUM syntax (ANALYZE ...).
-
由 Vadim B. Mikheev 提交于
2. VacuumStmt changed (for VACUUM ANALYZE...).
-
由 Vadim B. Mikheev 提交于
-
由 Marc G. Fournier 提交于
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...
-
由 Marc G. Fournier 提交于
Subject: [PORTS] Configure for DEC-Alpha Configure script properly detects alpha-dec-osf4.0 machine, but sets a default GENERIC template for it. I modified tempplate/.similar to add alpha-dec-osf4.0=alpha. Then configure properly set the template to alpha.
-
由 Marc G. Fournier 提交于
type check in numutils.c:ftoa() Pointed out by: "Martin J. Laubach" <mjl@emsi.priv.at>
-
由 Marc G. Fournier 提交于
Subject: [PATCHES] Patch for configure.in to not ask for CASSERT The following patch defaults to CASSERT, so it doesn't ask you. You can still use --enable-cassert and --disable-cassert to do it explicitly. Default: disabled
-
由 Marc G. Fournier 提交于
Subject: [PATCHES] date/time timezone patches (mail bounced?) Here are some hacks to get timezone behavior for the various time data types to be compatible with v6.0. Although we have some hooks already installed to get timezone info from the client to the server, it still isn't clear if that can correctly transfer enough timezone info to make the behavior the same as if timezone info were derived from the server as is now the case. We certainly won't resolve it in a day, so I think we are stuck with server-only timezones for v6.1.
-
由 Marc G. Fournier 提交于
OK, here are a passel of patches for the geometric data types. These add a "circle" data type, new operators and functions for the existing data types, and change the default formats for some of the existing types to make them consistant with each other. Current formatting conventions (e.g. compatible with v6.0 to allow dump/reload) are supported, but the new conventions should be an improvement and we can eventually drop the old conventions entirely. For example, there are two kinds of paths (connected line segments), open and closed, and the old format was '(1,2,1,2,3,4)' for a closed path with two points (1,2) and (3,4) '(0,2,1,2,3,4)' for an open path with two points (1,2) and (3,4) Pretty arcane, huh? The new format for paths is '((1,2),(3,4))' for a closed path with two points (1,2) and (3,4) '[(1,2),(3,4)]' for an open path with two points (1,2) and (3,4) For polygons, the old convention is '(0,4,2,0,4,3)' for a triangle with points at (0,0),(4,4), and (2,3) and the new convention is '((0,0),(4,4),(2,3))' for a triangle with points at (0,0),(4,4), and (2,3) Other data types which are also represented as lists of points (e.g. boxes, line segments, and polygons) have similar representations (they surround each point with parens). For v6.1, any format which can be interpreted as the old style format is decoded as such; we can remove that backwards compatibility but ugly convention for v7.0. This will allow dump/reloads from v6.0. These include some updates to the regression test files to change the test for creating a data type from "circle" to "widget" to keep the test from trashing the new builtin circle type.
-
- 22 4月, 1997 2 次提交
-
-
由 Vadim B. Mikheev 提交于
-
由 Marc G. Fournier 提交于
-
- 21 4月, 1997 2 次提交
-
-
由 Vadim B. Mikheev 提交于
-
由 Vadim B. Mikheev 提交于
-