| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
building contrib with USE_PGXS. To make it work all the way, the
pg_regress script would need to be included in the installation tree.
|
|
|
|
|
|
|
| |
relocated after installation. We can't trust the installation paths
inserted into Makefile.global by configure, so instead we must get the
paths from pg_config. This requires extending pg_config to support all
the separately-configurable path names, but that was on TODO anyway.
|
| |
|
|
|
|
| |
to avoid useless multiple executions of pg_config.
|
|
|
|
| |
to be less error-prone.
|
|
|
|
|
| |
out-of-memory --- that is, return NULL rather than dumping core.
Noted by Qingqing Zhou.
|
| |
|
| |
|
|
|
|
| |
adjusted from a patch by Simon.
|
|
|
|
|
|
|
|
| |
outer relation is empty did not work, per test case from Patrick Welche.
It tried to use nodeHashjoin.c's high-level mechanisms for fetching an
outer-relation tuple, but that code expected the hash table to be filled
already. As patched, the code failed in corner cases such as having no
outer-relation tuples for the first hash batch. Revert and rewrite.
|
| |
|
| |
|
|
|
|
|
|
|
| |
for int8 and related types. However we might be talking to a client
that has working int64; so pq_getmsgint64 really needs to check the
incoming value and throw an overflow error if we can't represent it
accurately.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
"optimization". When we find a potentially useful joinclause, we
have to add all its other required_relids to the result, not only the
other clause_relids. They are different in the case of a joinclause
whose applicability has to be postponed due to outer join. We have
to include the extra rels because otherwise, after best_inner_indexscan
masks the join rels with index_outer_relids, it will always fail to
find the joinclause as applicable. Per report from Husam Tomeh.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
in which invalid page data could be transiently written to disk by
concurrent bgwriter activity. There doesn't seem any risk of loss of
actual user data, but an empty page could possibly be left corrupt if a
crash occurs before the correct data gets written out. Pointed out by
Alvaro Herrera.
|
|
|
|
|
|
| |
It uses existing macros instead of touching directly.
ITAGAKI Takahiro
|
|
|
|
| |
Greg Sabino Mullane
|
|
|
|
| |
messages.
|
| |
|
|
|
|
|
|
| |
strings. This is consistent with SQL conventions, and since Bruce
already changed initdb in a way that assumed it worked like this, seems
we'd better make it work like this.
|
|
|
|
| |
given, per gripe from Michael Fuhr.
|
|
|
|
| |
Per report from Cesar Paipilla.
|
|
|
|
| |
by properly updating transaction state after AUTOCOMMIT.
|
|
|
|
| |
Backpatch to 8.0.X.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
errmsg("canceling query due to user request or statement timeout")));
|
| |
|
|
|
|
| |
Hiroshi Saito
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
sake of brevity and clarity.
Make pg_reload_conf(), pg_rotate_logfile(), and pg_cancel_backend()
return a boolean rather than an integer to indicate success or failure.
Along the way, make some minor cleanups to dbsize.c -- in particular,
use elog() rather than ereport() for "shouldn't happen" error
conditions, and remove some of the more flagrant violations of the
Postgres indentation conventions.
Catalog version bumped.
|
| |
|
|
|
|
|
|
|
| |
bytes. This shouldn't make any difference on x86 machines, where the size
happened to be 16 bytes anyway, but on 64-bit machines and machines with
slock_t int or wider, it will speed array indexing and hopefully reduce
SMP cache contention effects. Per recent experimentation.
|
| |
|
| |
|
|
|
|
| |
in parsing cursor declarations.
|
| |
|
|
|
|
| |
Roman Neuhauser. Update some obsolete comments for exec_eval_datum, too.
|
|
|
|
|
|
|
| |
recovered. I did not see any actual leak while testing this in CVS tip,
but 8.0 definitely has a problem with leaking the space temporarily
palloc'd by BufferSync(). In any case this seems a good idea to forestall
similar problems in future. Per report from Arjen van der Meijden.
|
|
|
|
| |
check for errors.
|
|
|
|
|
|
|
| |
to drop connections unceremoniously. Also some other marginal cleanups:
don't query getsockopt() repeatedly if it fails, and avoid having the
apparent definition of struct Port depend on which system headers you
might have included or not. Oliver Jowett and Tom Lane.
|
|
|
|
|
|
|
|
|
| |
> found in a pg_dump archive. It had problems with dollar-quote tags
broken across bufferload boundaries (this may explain bug report from
Rod Taylor), also with dollar-quote literals of the form $a$a$...,
and was also confused about the rules for backslash in double quoted
identifiers (ie, they're not special). Also put in placeholder support
for E'...' literals --- this will need more work later.
|