| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| |
|
|
| |
Simon Riggs
|
| |
|
|
|
| |
for user-facing errors, fix some poor choices of errcode, adhere to
message style guide.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
reloading of operator class information on each use of LookupOpclassInfo.
Had this been in place a year ago, it would have helped me find a bug
in the then-new 'operator family' code. Now that we have a build farm
member testing CLOBBER_CACHE_ALWAYS on a regular basis, it seems worth
expending a little bit of effort here.
|
| |
|
|
| |
Guillaume Lelarge
|
| |
|
|
|
|
|
| |
inappropriately generic-sounding names. This is more or less free since
we already forced initdb for the next beta, and it may prevent confusion or
name conflicts (particularly at the C-global-symbol level) down the road.
Per my proposal yesterday.
|
| |
|
|
|
|
|
|
|
| |
by short-circuiting schema search path and ambiguous-operator resolution
computations. Remarkably, this buys as much as 45% speedup of repetitive
simple queries that involve operators that are not an exact match to the
input datatypes. It should be marginally faster even for exact-match
cases, though I've not had success in proving an improvement in benchmark
tests. Per report from Guillame Smet and subsequent discussion.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Guillaume Lelarge
|
| |
|
|
| |
Joshua D. Drake
|
| |
|
|
| |
ERROR, not NOTICE.
|
| |
|
|
|
|
|
|
|
|
| |
is sane (eg, EXIT argument or first part of a qualified identifier), and cause
more-closely-nested record variables to take precedence over outer block
labels. This cures the breakage exhibited by Marko Kreen that 8.3 no longer
allowed a function's name to be used for a variable within the function, and
makes plpgsql's handling of block labels more like Oracle's. It's important
to fix this now because we are documenting the use of block labels as variable
qualifiers for the first time in 8.3.
|
| |
|
|
|
|
| |
not the image that (theoretically) should exist in the current directory.
Jørgen Austvik
|
| |
|
|
|
|
| |
useful consequence of the former liberal implicit casting to text;
namely that you can feed non-string values to quote_literal() and get
unsurprising results. Per discussion.
|
| | |
|
| | |
|
| |
|
|
|
| |
immutable and indexable. Also fix the volatility settings of some other
XML-related functions.
|
| | |
|
| | |
|
| |
|
|
| |
types.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
< * -Make 64-bit version of the MONEY data type
< * Add locale-aware MONEY type, and support multiple currencies
<
< http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php
< http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php
<
< * MONEY dumps in a locale-specific format making it difficult to
< restore to a system with a different locale
>
> * MONEY data type
>
> o -Make 64-bit version of the MONEY data type
> * Add locale-aware MONEY type, and support multiple currencies
>
> http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php
> http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php
>
> * MONEY dumps in a locale-specific format making it difficult to
> restore to a system with a different locale
> * Allow MONEY to be cast to/from other numeric data types
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to a UNION, CASE, or related construct are of the same domain type. The
main part of this routine smashes domains to their base types, which seems
necessary because the logic involves TypeCategory() and IsPreferredType(),
neither of which work usefully on domains. However, we can add a first
pass that just detects whether all the inputs are exactly the same type,
and if so accept that without question (so long as it's not UNKNOWN).
Per recent gripe from Dean Rasheed.
In passing, remove some tests for InvalidOid, which have clearly been dead
code for quite some time now, because getBaseType() would fail on that input.
Also, clarify the manual's not-very-precise description of the existing
algorithm's behavior.
|
| | |
|
| |
|
|
|
|
| |
entity numbers,
as in HTML.
|
| |
|
|
| |
regression test for XML names and numeric entities.
|
| | |
|
| | |
|
| |
|
|
|
| |
to reduce chattiness of logs. Per discussion.
Simon Riggs
|
| |
|
|
|
|
| |
subtlety that this function only returns a null terminator if it's
fed input that includes one; which, in the usage here, it's not.
This probably fixes bugs reported by Thomas Haegi.
|
| |
|
|
| |
Windows-specific MultiByteToWideChar/WideCharToMultiByte calls.
|
| | |
|
| |
|
|
|
| |
missed in possible future partial-drop scenarios. Improve comment.
Per report from Zoltan Boszormenyi.
|
| | |
|
| |
|
|
|
|
|
|
| |
clauselist_selectivity skip some analysis that's useless when there's only
one clause in the given list. Actually this can win even for not-so-simple
queries, because we also apply clauselist_selectivity to sublists such as the
quals matching an index; which are likely to have only a single entry even
when the total query is quite complicated.
|
| |
|
|
|
| |
it is needed --- basically don't remember the previous 'search_path'
after a drop schema because it might have failed but be created later.
|
| | |
|
| |
|
|
|
|
| |
if the locale has the thousands separator as "". This now matches the
to_char and psql numericlocale behavior. (Previously this data type was
basically useless for such setups.)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
where rtoffset == 0. In that case there is no need to change Var nodes,
and since filling in unset opfuncid fields is always safe, scribbling on the
input tree to that extent is not objectionable. This brings the cost of this
operation back down to what it was in 8.2 for simple queries. Per
investigation of performance gripe from Guillaume Smet.
|
