- 29 12月, 2005 8 次提交
-
-
由 Neil Conway 提交于
not be replaced with "ADD_P".
-
由 Bruce Momjian 提交于
documentation. Michael Fuhr
-
由 Tom Lane 提交于
setup. This protects against undesired changes in locale behavior if someone carelessly does setlocale(LC_ALL, "") (and we know who you are, perl guys).
-
由 Bruce Momjian 提交于
wording ("table" added).
-
由 Tom Lane 提交于
we want it to check the argument/result data types and no more. In particular, libperl shouldn't get initialized in this case.
-
由 Tom Lane 提交于
get_func_arg_info() for consistency with other names there. This code will probably be useful to other PLs when they start to support OUT parameters, so better to have it in the main backend. Also, fix plpgsql validator to detect bogus OUT parameters even when check_function_bodies is off.
-
由 Bruce Momjian 提交于
lacking it. Perhaps it was suppressed because of line length considerations, but "table" should appear.
-
由 Tom Lane 提交于
-
- 28 12月, 2005 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * Add missing optimizer selectivities for date, r-tree, etc > * Add missing rtree optimizer selectivity
-
由 Bruce Momjian 提交于
single column dump that has a \. value, so the load works properly. I also added documentation describing this issue.
-
由 Bruce Momjian 提交于
< * %Make row-wise comparisons work per SQL spec > * -Make row-wise comparisons work per SQL spec
-
由 Tom Lane 提交于
(previously we only did = and <> correctly). Also, allow row comparisons with any operators that are in btree opclasses, not only those with these specific names. This gets rid of a whole lot of indefensible assumptions about the behavior of particular operators based on their names ... though it's still true that IN and NOT IN expand to "= ANY". The patch adds a RowCompareExpr expression node type, and makes some changes in the representation of ANY/ALL/ROWCOMPARE SubLinks so that they can share code with RowCompareExpr. I have not yet done anything about making RowCompareExpr an indexable operator, but will look at that soon. initdb forced due to changes in stored rules.
-
由 Andrew Dunstan 提交于
Increase amount of shared buffers initdb tries to allocate to 4000, and add logic to try max_fsm_pages up to 200000, plus accompanying minor docs changes.
-
由 Bruce Momjian 提交于
if (c == '\\' && cstate->line_buf.len == 0) The problem with that is the because of the input and _output_ buffering, cstate->line_buf.len could be zero even if we are not on the first character of a line. In fact, for a typical line, it is zero for all characters on the line. The proper solution is to introduce a boolean, first_char_in_line, that we set as we enter the loop and clear once we process a character. I have restructured the line-reading code in copy.c by: o merging the CSV/non-CSV functions into a single function o used macros to centralize and clarify the buffering code o updated comments o renamed client_encoding_only to encoding_embeds_ascii o added a high-bit test to the encoding_embeds_ascii test for performance o in CSV mode, allow a backslash followed by a non-period to continue being processed as a data value There should be no performance impact from this patch because it is functionally equivalent. If you apply the patch you will see copy.c is much clearer in this area now and might suggest additional optimizations. I have also attached a 8.1-only patch to fix the CSV \. handling bug with no code restructuring.
-
- 27 12月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 26 12月, 2005 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
* %Make row-wise comparisons work per SQL spec Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but the SQL standard requires it to be processed as a column-by-column comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'.
-
由 Neil Conway 提交于
- use "bool" rather than "int" for boolean variables - use "PLy_malloc" rather than "malloc" in two places - define "PLy_strdup", and use it rather than malloc() + strcpy() in two places (which should have been memcpy(), anyway). - remove a bunch of redundant parentheses from expressions that do not need the parentheses for code clarity
-
- 25 12月, 2005 9 次提交
-
-
由 Bruce Momjian 提交于
#define HIGHBIT (0x80) #define IS_HIGHBIT_SET(ch) ((unsigned char)(ch) & HIGHBIT) and removed CSIGNBIT and mapped it uses to HIGHBIT. I have also added uses for IS_HIGHBIT_SET where appropriate. This change is purely for code clarity.
-
由 Neil Conway 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Add comment marker for PG_ENCODING_BE_LAST.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 24 12月, 2005 5 次提交
-
-
由 Tatsuo Ishii 提交于
See: Subject: [HACKERS] bugs with certain Asian multibyte charsets From: Tatsuo Ishii <ishii@sraoss.co.jp> To: pgsql-hackers@postgresql.org Date: Sat, 24 Dec 2005 18:25:33 +0900 (JST) for more details/
-
由 Tom Lane 提交于
postgresql.conf.sample too.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
differ by more than the last directory component. Instead of insisting that they match up to the last component, accept whatever common prefix they have, and try to replace the non-matching part of bin_path with the non-matching part of target_path in the actual executable's path. In one way this is tighter than the old code, because it insists on a match to the part of bin_path we want to substitute for, rather than blindly stripping one directory component from the executable's path. Per gripe from Martin Pitt and subsequent discussion.
-
由 Peter Eisentraut 提交于
of having no password.
-
- 23 12月, 2005 5 次提交
-
-
由 Tatsuo Ishii 提交于
Also make the code more robust by searching for target encoding in the internal charset map. Problem reported by Sagi Bashari on 2005/12/21. See "[BUGS] BUG #2120: Crash when doing UTF8<->ISO_8859_8 encoding conversion" on pgsql-bugs list for more details.
-
由 Tom Lane 提交于
modify the previous \password patch to use it instead of depending on a not-officially-exported function. Per discussion.
-
由 Bruce Momjian 提交于
SET.
-
由 Bruce Momjian 提交于
> > A more complex solution would be to save multiple plans for different > cardinality and use the appropriate plan based on the EXECUTE values. >
-
由 Tom Lane 提交于
equal: if strcoll claims two strings are equal, check it with strcmp, and sort according to strcmp if not identical. This fixes inconsistent behavior under glibc's hu_HU locale, and probably under some other locales as well. Also, take advantage of the now-well-defined behavior to speed up texteq, textne, bpchareq, bpcharne: they may as well just do a bitwise comparison and not bother with strcoll at all. NOTE: affected databases may need to REINDEX indexes on text columns to be sure they are self-consistent.
-