| Age | Commit message (Collapse) | Author |
|---|
|
Oliver Elphick. A few other minor cleanups while at it.
|
|
multibyte encodings.
|
|
from Hiroshi.
|
|
Fixes time zone problems introduced by Thomas' implementation of
TIMESTAMP WITHOUT TIME ZONE which caused the behavior of the previously
appropriate routine, timestamp_date(), to change for the worse in this
context.
|
|
|
|
per bug report from Laurette Cisneros.
|
|
formats will be taken as 2000, not year zero. Per bug report from
Aasmund Midttun Godal. Fix from Karel Zak.
|
|
token. Seems to be isolated to datetime.c and datetime.h.
|
|
values; it's not portable to call them with signed chars. I recall doing
this for the last release, but a few more uncasted calls have snuck in.
|
|
|
|
when decoding date fields.
|
|
cases which should have worked but did not.
Now supports julian day (J2452271), ISO time labels (T040506) and various
combinations of spaces and run-togethers of dates, times, and time zones.
All regression tests pass, and I have more tests to add after the 7.2
release (don't want to require changes to the ancillary horology result
files until after then).
|
|
machines. I have just been observing some scenarios where set_ps_display
accounts for more than 10% of the backend CPU, and this loop has to be
the reason.
|
|
Thanks to Greg Sabino Mullane <greg@turnstep.com> for finding the problem.
|
|
if presented with a tuple in process of being moved by VACUUM. Per
bug report from Brian Hirt.
|
|
|
|
per complaint from Kemin Zhou.
Fix lack of precision in numeric stddev/variance.
|
|
From Manuel Sugawara, approved by Karel Zak.
|
|
|
|
remove brain-dead rule that double quotes are needed if and only if the
datatype is pass-by-reference; neither direction of the implication holds
water. Instead, examine the actual data string to see if it contains
any characters that force us to quote it.
Add some documentation about quoting of array values, which was previously
explained nowhere AFAICT.
|
|
per bug report from Stefan Hadjistoytchev. There are some cases
where the dot notation works, but there are more where it doesn't.
Eventually ought to consider fixing the parser to allow cases like
func().field, but for now this is the simplest patch.
|
|
have an INSERT...SELECT as the first or only action. Per bug report
from Sergio Pili.
|
|
pgsql-patches.
|
|
|
|
Per report from Bernd Tegge.
|
|
Linux box's time zone database.
Do not allow 'current' as a date/time input value.
|
|
Problem reported by Manuel Sugawara (masm@fciencias.unam.mx).
|
|
|
|
display (with a typemod) and function arg/result type display (without
a typemod).
|
|
|
|
with other data types, per disucssion. Encoding issue still open.
|
|
|
|
o they sometimes returns a result garbage string appended.
o they do not work if client encoding is different from server
encoding
|
|
encodings.
|
|
search lists was broken in such a way that only the most recent
instance of a given hash code would ever be searched, thus possibly
missing longer matches further back. Fixing this gave 5 to 10%
compression improvement on some text test cases. Additional small
tweaks to improve speed of inner loops a little bit. There is no
compatibility issue created by this change, since the compressed data
format and decompression algorithm don't change.
|
|
This seems the right thing for most usages, but I notice two places
where it is the wrong thing. One is that the default permissions on
TOAST rels should be no-access, not world-readable; the other is that
PrepareForTupleInvalidation doesn't really need to spend time looking
at tuples of TOAST relations.
|
|
bpchar, bit, numeric with typmod -1. Alter format_type so that this
representation is printed when the typmod is -1. This ensures that
tables having such columns can be pg_dump'd and reloaded correctly.
Also, remove the rather useless and non-SQL-compliant default
precision and scale for type NUMERIC. A numeric column declared as
such (with no precision/scale) will now have typmod -1 which means
that numeric values of any precision/scale can be stored in it,
without conversion to a uniform scale. This seems significantly
more useful than the former behavior. Part of response to bug #513.
|
|
used inside fk constraints, since some of the checks
in the trigger did a SELECT oid. Since the oid wasn't
actually used, I changed this to SELECT 1. My test
case with non-oid tables now works and fk regression
appears to run fine on my machine.
Stephan Szabo
|
|
Brent Verner, with review and kibitzing from Tom Lane.
|
|
Per report from Bernd Tegge, 10-Nov-01.
|
|
(surprised no one has reported these yet...)
|
|
|
|
|
|
initdb/regression tests pass.
|
|
recreated since the start of our transaction, our first reference to it
errored out because we'd try to reuse our old relcache entry for it.
Do this by accepting SI inval messages just before relcache search in
heap_openr, so that dead relcache entries will be flushed before we
search. Also, break heap_open/openr into two pairs of routines,
relation_open(r) and heap_open(r). The relation_open routines make
no tests on relkind and so can be used to open anything that has a
pg_class entry. The heap_open routines are wrappers that add a relkind
test to preserve their established behavior. Use the relation_open
routines in several places that had various kluge solutions for opening
rels that might be either heap or index rels.
Also, remove the old 'heap stats' code that's been superseded by Jan's
stats collector, and clean up some inconsistencies in error reporting
between the different types of ALTER TABLE.
|
|
|
|
|
|
|
|
spacing. Also adds space for one-line comments.
|
|
breaking existing pg_dump scripts, which try to assign the result of
count(*) to an int2 variable. catversion bumped.
|
