| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
system calls on AIX (and probably other machines too).
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Add type conversion functions for floating point numbers.
Check for zero in unary minus floating point code (IEEE allows an
explicit negative zero which looks ugly in a query result!).
Ensure circle type has non-negative radius.
|
| | |
|
| |
|
|
| |
Subject: [PATCHES] oracle_compat functions core dumping on NULL-fields
|
| |
|
|
| |
return if storage is not allocated. Ref: Vadim 97/05/01
|
| |
|
|
| |
by case-insensitive SQL parser.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fd = FileNameOpenFile(path, O_RDWR|O_CREAT|O_EXCL, 0600);
/*
* If the file already exists and is empty, we pretend that the
* create succeeded. During bootstrap processing, we skip that check,
* because pg_time, pg_variable, and pg_log get created before their
* .bki file entries are processed.
*
> * As the result of this pretence it was possible to have in
> * pg_class > 1 records with the same relname. Actually, it
> * should be fixed in upper levels, too, but... - vadim 05/06/97
> */
|
| |
|
|
|
|
| |
Assert ( --Vnpages > 0 );
and
Assert ( --Fnpages > 0 );
|
| |
|
|
|
|
|
|
|
| |
when btree used in innerscan with run-time key which value
passed by pointer.
Fix: keys ordering stuff moved to _bt_first().
Pointed by Thomas Lockhart.
|
| |
|
|
| |
if 1st bucket chain is empty then need to continue scan in the rest buckets.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
bool _use_geqo_ = true;
#else
bool _use_geqo_ = false;
#endif
_use_geqo_ is settable via SET var TO ...
|
| |
|
|
| |
in target list.
|
| |
|
|
|
|
|
|
|
|
| |
Subject: [HACKERS] Inputting money
I notice that I have to put single quotes around money amounts if there
is a decimal point in the value. I appears to be happening because there
is something changing things like "123.45" to "123.450000" and the code
has a problem with that. There may be a better way to fix this but here
is a simple change to cash.c that lets it accept trailing zeroes.
|
| | |
|
| |
|
|
|
| |
Add comparison operators to boolean and smaller/larger operators to datetime
and timespan. Fix int4 overflow math problem in timespan comparison operators.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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... :-)
|
| |
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
| |
* npages = index_pages * selectivity_of_1st_attr_clause(s)
|
| |
|
|
|
| |
joininfo (in add_join_clause_info_to_rels()) : clause may be
commutted later.
|
| |
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
SET cost_heap(cost_index) TO ...
|
| | |
|
| | |
|
| |
|
|
| |
Satoshi Ishikawa <power@sekine.densi.gifu-u.ac.jp>
|
| | |
|
| | |
|
| |
|
|
| |
2. vacuum() call changed (ANALYZE).
|
| |
|
|
| |
2. New VACUUM syntax (ANALYZE ...).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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...
|
| |
|
|
|
|
| |
type check in numutils.c:ftoa()
Pointed out by: "Martin J. Laubach" <mjl@emsi.priv.at>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
the last week on Hackers...(A coulpe of clippings of the final
verdict are included below + the diff).
From: Wayde Nie <niew@phoenix.cis.mcmaster.ca>
|
| | |
|
| |
|
|
| |
added to WriteBuffer(), FlushBuffer(), WriteNoReleaseBuffer().
|
| |
|
|
| |
building.
|
