| Commit message (Collapse) | Author | Age |
|
|
|
| |
report from dvice_null@yahoo.com.
|
|
|
|
|
|
| |
function to the string type and add a couple of macros for string handling.
In passing, fix an off-by-one bug of mine.
|
|
|
|
| |
from Rushabh Lathia.
|
| |
|
|
|
|
| |
with URL pointing to email discussion.
|
|
|
|
|
|
|
|
|
| |
the default. This setting enables constraint exclusion checks only for
appendrel members (ie, inheritance children and UNION ALL arms), which are
the cases in which constraint exclusion is most likely to be useful. Avoiding
the overhead for simple queries that are unlikely to benefit should bring
the cost down to the point where this is a reasonable default setting.
Per today's discussion.
|
|
|
|
|
| |
debug_query_string; this allows current_query() to be more accurate;
docs updated; per idea from Tom
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
OutputFunctionCall, and friends. This allows SPI-using functions to invoke
datatype I/O without concern for the possibility that a SPI-using function
will be called (which could be either the I/O function itself, or a function
used in a domain check constraint). It's a tad ugly, but not nearly as ugly
as what'd be needed to make this work via retail insertion of push/pop
operations in all the PLs.
This reverts my patch of 2007-01-30 that inserted some retail SPI_push/pop
calls into plpgsql; that approach only fixed plpgsql, and not any other PLs.
But the other PLs have the issue too, as illustrated by a recent gripe from
Christian Schröder.
Back-patch to 8.2, which is as far back as this solution will work. It's
also as far back as we need to worry about the domain-constraint case, since
earlier versions did not attempt to check domain constraints within datatype
input. I'm not aware of any old I/O functions that use SPI themselves, so
this should be sufficient for a back-patch.
|
|
|
|
| |
'query_string' from current_query().
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
not include postgres.h nor anything else it doesn't directly need. Add
#includes to calling files as needed to compensate. Per my proposal of
yesterday.
This should be noted as a source code change in the 8.4 release notes,
since it's likely to require changes in add-on modules.
|
|
|
|
|
|
| |
to pass the full username@realm string to the authentication instead of
just the username. This makes it possible to use pg_ident.conf to authenticate
users from multiple realms as different database users.
|
|
|
|
|
| |
authentication options to be set in pg_hba.conf on a per-line basis, to
override the defaults set in postgresql.conf.
|
|
|
|
|
|
| |
hardcoded paths for SSL rootcert/crl/clientcert/key.
As noted by Andrew Chernow
|
|
|
|
|
|
|
|
| |
consistent. Currently, in csvlog, vxid of an auxiliary process isn't
displayed. On the other hand, in stderr/syslog, invalid vxid (-1/0) of
that is displayed.
Fujii Masao
|
| |
|
| |
|
| |
|
|
|
|
| |
Per Nathan Boley.
|
| |
|
|
|
|
| |
Fix \do and trigger display for the patch too.
|
|
|
|
|
|
| |
like \dt does, in that it requires a \dXS to see system items.
Greg Sabino Mullane
|
|
|
|
| |
same way the unix build now does.
|
|
|
|
| |
consistency.
|
| |
|
|
|
|
|
|
|
| |
particular this allows EmitWarningsOnPlaceholders messages to show up in the
postmaster log by default. Update elog.h comment to make it clearer what INFO
is for, and fix one example in the SGML docs that was misusing it. Per my
gripe of yesterday.
|
|
|
|
|
| |
where there's no limit on the size of datum we'll try to compress.
Other 8.4 tweaks to the behavior remain in place. Per discussion.
|
|
|
|
|
| |
earlier than all the other sizeof checks, and it certainly fails to follow
the order suggested at the file head. Rearrange.
|
|
|
|
|
|
|
|
| |
If the table was smaller than REL_TRUNCATE_FRACTION (= 16) pages, we always
tried to acquire AccessExclusiveLock on it even if there was no empty pages
at the end.
Report by Simon Riggs. Back-patch all the way to 7.4.
|
| |
|
| |
|
| |
|
|
|
|
| |
document change.
|
|
|
|
| |
restricted.
|
|
|
|
|
|
|
| |
default expressions to a function call, eval_const_expressions must recurse on
those expressions. Else they don't get simplified, and in particular we fail
to insert additional default arguments if any functions needing defaults are
in there. Per report from Rushabh Lathia.
|
|
|
|
|
|
|
|
| |
a more complete framework for writing custom option processing routines
by user-defined access methods.
Catalog version bumped due to the general API changes, which are going to
affect user-defined "amoptions" routines.
|
|
|
|
|
|
|
|
|
|
|
| |
performing dumps and restores in accordance with a security policy that
forbids logging in directly as superuser, but instead specifies that you
should log into an admin account and then SET ROLE to the superuser.
In passing, clean up some ugly and mostly-broken code for quoting shell
arguments in pg_dumpall.
Benedek László, with some help from Tom Lane
|
|
|
|
|
|
| |
re-loading a library already loaded into the postmaster.
ITAGAKI Takahiro
|
|
|
|
| |
present in the placeholder. Noted while testing pg_stat_statements.
|
|
|
|
|
|
| |
when --with-system-tzdata is not used.
initial patch by Richard Evans
|
|
|
|
|
| |
of pwd vs. pwd -W is correctly a function of the build system, not the
host system.
|
|
|
|
| |
Author: Richard Evans <richard.evans@blueallegro.net>
|
|
|
|
| |
ITAGAKI Takahiro
|
|
|
|
|
|
| |
statistics.
Takahiro Itagaki
|
|
|
|
|
|
|
|
| |
except the caller can specify the encoding to work in; this will be needed
for pg_stat_statements. In passing, do some marginal efficiency hacking
and clean up some comments. Also, prevent the single-byte-encoding code
path from fetching one byte past the stated length of the string (this
last is a bug that might need to be back-patched at some point).
|
|
|
|
|
| |
be written for *non*-temp tables only. Report and test case by Mark
Kirkwood and Simon Riggs.
|
|
|
|
|
|
| |
when loaded via shared_preload_libraries. Needed for support of
pg_stat_statements, or pretty much anything else that wants a GUC to
control size of a shared memory allocation.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
initialization, to give loadable modules a reasonable place to perform
creation of any shared memory areas they need. This is the logical conclusion
of our previous creation of RequestAddinShmemSpace() and RequestAddinLWLocks().
We don't need an explicit shmem_shutdown_hook, because the existing
on_shmem_exit and on_proc_exit mechanisms serve that need.
Also, adjust SubPostmasterMain so that libraries that got loaded into the
postmaster will be loaded into all child processes, not only regular backends.
This improves consistency with the non-EXEC_BACKEND behavior, and might be
necessary for functionality for some types of add-ons.
|
|
|
|
|
|
|
| |
practically free given prior 8.4 changes in plancache and portal management,
and it makes it a lot easier for ExecutorStart/Run/End hooks to get at the
query text. Extracted from Itagaki Takahiro's pg_stat_statements patch,
with minor editorialization.
|