| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
- 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...
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
or view that's been dropped and then recreated with the same name (but,
perhaps, different columns). Eventually we'd like to support this but
for now all we can do is fail cleanly, rather than possibly coredumping
if we proceed using the obsolete rule.
|
| |
|
|
|
|
|
|
| |
to specific base or join RelOptInfo nodes during planning. This preserves
the more-intuitive behavior of 7.0.* --- if you write an expensive clause
(such as a sub-select) last, it should get evaluated last. Someday we
ought to try to have some intelligence about the order of evaluation of
WHERE clauses, but for now we should not override what the user wrote.
|
| |
|
|
| |
Patches contributed by Eiji Tokuya (e-tokuya@sankyo-unyu.co.jp)
|
| |
|
|
|
| |
converting char* strings to type 'name'. Imagine my surprise when 7.1
release coredumped upon start when compiled --enable-multibyte ...
|
| |
|
|
|
|
|
|
| |
only possible failure is in pq_flush, which will log a (better!) report
anyway --- so pq_endmessage is just cluttering the log with a redundant
entry. This matters when a client crashes partway through a large query,
since we will emit many broken-pipe reports before finishing the query
and exiting.
|
| |
|
|
| |
Rocco Altier <roccoa@routescape.com>.
|
| |
|
|
|
|
|
|
| |
lists should be reverse-compiled into targetlist index numbers, because
that's the only interpretation the parser allows for a constant in these
clauses. (Ergo, the only way they could have gotten into the list in
the first place is to have come from the targetlist; so this should always
work.) Per problem report from Peter E.
|
| |
|
|
|
|
|
|
| |
join clauses. The mergejoin executor wants all the join clauses to appear
as merge quals, not as extra joinquals, for these kinds of joins. But the
planner would consider plans in which partially-sorted input paths were
used, leading to only some of the join clauses becoming merge quals.
This is fine for inner/left joins, not fine for right/full joins.
|
| |
|
|
| |
also go there.
|
| | |
|
| | |
|
| |
|
|
| |
- Fix crash due to null string pointer in some tar files with some libs
|
| |
|
|
|
|
| |
Although it was now using the right equation, it was making bogus choices
of the precision to compute intermediate results to. I'm not sure this
is really right even yet, but it's better than before ...
|
| |
|
|
| |
is not a complete declaration.
|
| |
|
|
| |
so I removed it.
|
| | |
|
| |
|
|
|
|
| |
(fix by Hiroki kataoka).
2) Ensure the definition of atof()(#include stdlib.h).
(suggestion by Masaaki Sakaida).
|
| |
|
|
|
|
|
| |
(which failed miserably during DST) to just compare against a time
derived from a timestamp value.
Certainly not a direct check for a correct result, but should work
at any time of year.
|
| |
|
|
|
|
| |
it needs to ensure that data structures attached to fmgr info records in
the trees will stick around that long, too. Current code was crashing
on cases like datatypes with old-style I/O functions.
|
| | |
|
| |
|
|
| |
no room for a record on last log page.
|
| | |
|
| |
|
|
| |
they have children. As it stood, -d dump mode was badly broken.
|
| |
|
|
|
| |
This patch is Peter E's, but I'm applying it on his behalf so it'll get
into 7.1RC3 tonight (I'm guessing Peter went to bed already).
|
| |
|
|
| |
Jason Tishler's credit, if it's broken it's my fault ...
|
| |
|
|
|
| |
datatype. Perhaps someday we can figure out a way of getting reproducible
results from testing this type, but for now ...
|
| |
|
|
| |
Thanks to Tom.
|
| |
|
|
| |
starting with '$'.
|
| | |
|
| | |
|
| |
|
|
| |
- Dump CHECK constraints in OID order
|
