Age | Commit message (Collapse) | Author |
|
is actively dangerous, per bug report from Ewald Geschwinde 14-May-02,
and several of the rest look suspicious to me. Since there is no longer
any significant value in retail pfree's in these functions, just get
rid of all of them for safety's sake.
|
|
lower subscript bounds change.
|
|
Will be patched separately but equivalently in HEAD for 7.3.
|
|
Fix bug in extract/date_part for milliseconds/miscroseconds and
timestamp/timestamptz combo. Now extract/date_part returns
seconds*1000 or 1000000 + fraction part as the manual stats.
regression test are also fixed.
See the thread in pgsql-hackers:
Subject: Re: [HACKERS] timestamp_part() bug?
Date: Sat, 02 Mar 2002 11:29:53 +0900
|
|
Fix a few apparently-wrong TZ vs DTZ declarations.
Same patch as added to HEAD.
|
|
Also, 'fourty' -> 'forty'.
|
|
originally created with, so that the set of visible tuples does not
change as a result of other activity. This essentially makes PG cursors
INSENSITIVE per the SQL92 definition. See bug report of 13-Feb-02.
|
|
|
|
|
|
|
|
mess up after an aborted VACUUM FULL, per today's pghackers discussion.
Add a suitable HeapTupleSatisfiesToast routine. Remove useless special-
case test in HeapTupleSatisfiesVisibility macro for xmax =
BootstrapTransactionId; perhaps that was needed at one time, but it's
a waste of cycles now, not to mention actively wrong for SnapshotAny.
Along the way, add some much-needed comments to tqual.c, and simplify
toast_fetch_datum, which no longer needs to assume it may see chunks
out-of-order.
|
|
This saves one open file descriptor per backend, and avoids an
annoying NOTICE on Cygwin (which has trouble deleting open files).
Bug appears to date back to original coding of init_irels, circa 1992.
|
|
temporary file. This seems to be a known failure mode under Cygwin,
so we might as well expend the extra line of code to be tidy.
|
|
Thanks to Bruce for spotting it and Tom Lane for diagnosing it.
Since horology test output is changing anyway, add some date/time input
tests to horology.sql. Some of these should move to the tests for the
individual data types, and we perhaps should add an entire new test
for "timezone" to allow manipulating the current time zone without
risking damage to the results of other tests.
|
|
as either HEAP_XMAX_COMMITTED or HEAP_XMAX_INVALID once the updating
transaction is gone. Otherwise some other transaction may come along
and try to test the commit status of t_xmax later --- which could be
after VACUUM has recycled the CLOG status for that xact. Bug introduced
in post-beta4 bug fix.
|
|
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.
|