| Age | Commit message (Collapse) | Author |
|---|
|
|
|
not TRUE. Otherwise we break pl call handler functions. fmgr_oldstyle
will take care of making sure the semantics are the same for C functions.
Clean up some slightly grotty coding in 7.0 pg_class reading, also.
|
|
|
|
- Fix view dumping SQL for V7.0
- Fix bug when getting view oid with long view names
- Treat SEQUENCE SET TOC entries as data entries rather than schema
entries.
- Make allowance for data entries that did not have a data dumper
routine (eg. SEQUENCE SET)
|
|
|
|
set null/default).
|
|
to their children, leading to misbehavior if they had any children that paid
attention to chgParam (most plan node types don't). Append's bug has been
there a long time, but nobody had noticed because it used to be difficult
to create a query where an Append would be used below the top level of a
plan; so there were never any parameters getting passed down. SubqueryScan
is new in 7.1 ... and I'd modeled its behavior on Append :-(
|
|
passed, which occurs when no rows are retrieved by a SELECT.
Mea maxima culpa ... I should have caught this.
|
|
|
|
going to have any at all.
|
|
running deferred triggers. They are really part of the regular
transaction, and they could take awhile.
|
|
routine DetermineLocalTimeZone(). In that routine, be more wary of
broken mktime() implementations than the original code was: don't allow
mktime to change the already-set y/m/d/h/m/s information, and don't
use tm_gmtoff if mktime failed. Possibly this will resolve some of
the complaints we've been hearing from users of Middle Eastern timezones
on RedHat.
|
|
support two - KOI8-R and KOI8-U (latter is superset of the former if
not to take to the account pseudographics)
Andy Rysin
|
|
either :-(.
|
|
Oleg Bartunov
|
|
give consistent results for all datatypes. Types float4, float8, and
numeric were broken for NaN values; abstime, timestamp, and interval
were broken for INVALID values; timetz was just plain broken (some
possible pairs of values were neither < nor = nor >). Also clean up
text, bpchar, varchar, and bit/varbit to eliminate duplicate code and
thereby reduce the probability of similar inconsistencies arising in
the future.
|
|
Per bug report from Lieven Van Acker, 5/2/01.
|
|
|
|
|
|
|
|
<Jason.Tishler@dothill.com>.
|
|
Convert back to Unix style --- it seems some versions of nmake insist
on this.
|
|
the way to handle this.
|
|
properly on 64 bit systems.
Change submitted by Marc Poinot (Marc.Poinot@onera.fr)
|
|
|
|
This is an extension to the SQL9x standard, but is consistant with usage
of the underlying date_part() function used to implement it.
Example: EXTRACT('YEAR',...)
No impact on regression tests.
|
|
2) fix a bug reported by Jan Wieck.
psqlodbc is 7.01.0005 now.
|
|
number of columns than it was expecting, for reasons that are now
documented in the code...
|
|
join. This is needed to avoid improper evaluation of expressions that
should be nulled out, as in Victor Wagner's bug report of 4/27/01.
Pretty ugly solution, but no time to do anything better for 7.1.1.
|
|
Patches contributed by Victor Wagner.
|
|
it's bogus, try building a btree index on the regress tests' abstime_tbl.)
|
|
Without this, it was making some pretty silly decisions about whether an
expensive sub-SELECT should be the inner or outer side of a join...
|
|
- pgsql v7.0 compatbility
|
|
counted off by lines ...
|
|
|
|
|
|
complaints about 'Cache reference leak'. Per report from Don Baccus.
|
|
resolved the stack over flow errors reported by Johann Zuschlag.
2) Support {oj syntax for 71. servers.
|
|
1) [ODBC] Psqlodbc and Centura: here it is a patch
posted by Matteo Cavalleli
2) [ODBC] pgsqODBC binding parameters II
posted by Ludek Finstrle
3) Invalid Page Fault in PSQLODBC.DLL
personal mail from Johann Zuschlag
Hiroki Kataoka kataoka@interwiz.koganei.tokyo.jp
|
|
(Not sure such an index is actually useful, but just because it's
useless doesn't mean pg_dump should coredump.)
|
|
userids are the same. Per today's pghackers discussion.
|
|
-o option) are properly dequoted. Also, always pass an explicit -D option
to postmaster, don't rely on it being set in postmaster.opts.
|
|
|
|
|
|
function arguments in join queries: copy the tuples into
TransactionCommandContext so they don't get recycled too soon. This is
horrid, but not any worse than 7.0 or before, which also leaked such
tuples until end of query. A proper fix will require allowing tuple
datums to be physically stored inside larger tuple datums, which opens
up a bunch of issues that can't realistically be solved for 7.1.1.
|
|
given.
|
|
functions of join or subselect aliases. It'd be awfully nice if this
code knew for sure whether it was dealing with 'x.f' or 'f(x)' syntax;
maybe we can fix that in a future cycle.
|
|
spaces (e.g., '\!ls -l'). Also correct a comment.
|
|
already worked fine for whole rows of tables, but not so well for views...
|
|
|
