- 26 11月, 2009 1 次提交
-
-
由 Tom Lane 提交于
the time, rather than hoping we can tell whether the terminal supports UTF8 characters. Per discussion.
-
- 25 11月, 2009 2 次提交
-
-
由 Peter Eisentraut 提交于
Author: Erik Rijkers <er@xs4all.nl>
-
由 Michael Meskes 提交于
-
- 24 11月, 2009 2 次提交
-
-
由 Peter Eisentraut 提交于
Author: Euler Taveira de Oliveira <euler@timbira.com>
-
由 Tom Lane 提交于
newline representations. Per buildfarm results and subsequent discussion. Sync up a couple of other places that had their own policies.
-
- 23 11月, 2009 5 次提交
-
-
由 Magnus Hagander 提交于
Hiroshi Saito
-
由 Heikki Linnakangas 提交于
be part of multixacts, so allocate a slot for each prepared transaction in the "oldest member" array in multixact.c. On PREPARE TRANSACTION, transfer the oldest member value from the current backends slot to the prepared xact slot. Also save and recover the value from the 2pc state file. The symptom of the bug was that after a transaction prepared, a shared lock still held by the prepared transaction was sometimes ignored by other transactions. Fix back to 8.1, where both 2PC and multixact were introduced.
-
由 Tom Lane 提交于
a bit more consistent and less obviously written by different people at different times.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
We have used -w for a long time as a means of reducing the reported diff volume when one element of a result table isn't of the expected width. However, most of the time the results just pass anyway, so this isn't as important as it once was. Meanwhile, the risk of missing potentially significant deviations has gone up, particularly with psql's ability to report error cursor positions. So, let's switch over to space-sensitive comparisons. Per my proposal of yesterday. (All the expected files that I can test here seem to be ready for this already, but we'll see what the buildfarm thinks about others.)
-
- 22 11月, 2009 4 次提交
-
-
由 Heikki Linnakangas 提交于
Jan Urbanski
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
in the formerly-always-blank columns just to left and right of the data. Different marking is used for a line break caused by a newline in the data than for a straight wraparound. A newline break is signaled by a "+" in the right margin column in ASCII mode, or a carriage return arrow in UNICODE mode. Wraparound is signaled by a dot in the right margin as well as the following left margin in ASCII mode, or an ellipsis symbol in the same places in UNICODE mode. "\pset linestyle old-ascii" is added to make the previous behavior available if anyone really wants it. In passing, this commit also cleans up a few regression test files that had unintended spacing differences from the current actual output. Roger Leigh, reviewed by Gabrielle Roth and other members of PDXPUG.
-
由 Peter Eisentraut 提交于
the client encoding is UTF-8. a limited version of a patch proposed by Itagaki Takahiro
-
- 21 11月, 2009 2 次提交
-
-
由 Tom Lane 提交于
list, minus a few specific words that have to be treated specially. This replaces a hard-wired list of keywords that would have needed manual maintenance, and was not getting it. The 8.4 coding was already missing these words, causing ecpg to incorrectly treat them as reserved words: CALLED, CATALOG, DEFINER, ENUM, FOLLOWING, INVOKER, OPTIONS, PARTITION, PRECEDING, RANGE, SECURITY, SERVER, UNBOUNDED, WRAPPER. In HEAD we were additionally missing COMMENTS, FUNCTIONS, SEQUENCES, TABLES. Per gripe from Bosco Rama.
-
由 Tom Lane 提交于
checked to determine whether the trigger should be fired. For BEFORE triggers this is mostly a matter of spec compliance; but for AFTER triggers it can provide a noticeable performance improvement, since queuing of a deferred trigger event and re-fetching of the row(s) at end of statement can be short-circuited if the trigger does not need to be fired. Takahiro Itagaki, reviewed by KaiGai Kohei.
-
- 20 11月, 2009 1 次提交
-
-
由 Peter Eisentraut 提交于
fixed in 8.4 and 8.5 Author: Guillaume Lelarge <guillaume@lelarge.info>
-
- 19 11月, 2009 2 次提交
-
-
由 Tom Lane 提交于
output filename if CSV logging was enabled and only one of the two possible output files got rotated during a particular call (which would, in fact, typically be the case during a size-based rotation). This would amount to about MAXPGPATH (1KB) per rotation, and it's been there since the CSV code was put in, so it's surprising that nobody noticed it before. Per bug #5196 from Thomas Poindessous.
-
由 Tom Lane 提交于
strength of database passwords, and create a sample implementation of such a hook as a new contrib module "passwordcheck". Laurenz Albe, reviewed by Takahiro Itagaki
-
- 17 11月, 2009 2 次提交
-
-
由 Tom Lane 提交于
adopted for EXPLAIN. This will allow additional options to be implemented in future without having to make them fully-reserved keywords. The old syntax remains available for existing options, however. Itagaki Takahiro
-
由 Tom Lane 提交于
non-Var sort/group expressions using ressortgroupref labels instead of depending entirely on equal()-ity of the upper node's tlist expressions to the lower node's. This avoids emitting the wrong outputs in cases where there are textually identical volatile sort/group expressions, as for example select distinct random(),random() from generate_series(1,10); Per report from Andrew Gierth. Backpatch to 8.4. Arguably this is wrong all the way back, but the only known case where there's an observable problem is when using hash aggregation to implement DISTINCT, which is new as of 8.4. So for the moment I'll refrain from backpatching further.
-
- 15 11月, 2009 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
mergejoin to shield it from doing mark/restore and refetches. Put an explicit flag in MergePath so we can centralize the logic that knows about this, and add costing logic that considers using Materialize even when it's not forced by the previously-existing considerations. This is in response to a discussion back in August that suggested that materializing an inner indexscan can be helpful when the refetch percentage is high enough.
-
由 Tom Lane 提交于
Set search_path explicitly, don't use IF EXISTS, etc.
-
- 14 11月, 2009 6 次提交
-
-
由 Magnus Hagander 提交于
Win32. Also refactor the code around it to be more clear. Jesse Morris
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
default be "throw error on conflict", as per discussions. The GUC variable is plpgsql.variable_conflict, with values "error", "use_variable", "use_column". The behavior can also be specified per-function by inserting one of #variable_conflict error #variable_conflict use_variable #variable_conflict use_column at the start of the function body. The 8.5 release notes will need to mention using "use_variable" to retain backward-compatible behavior, although we should encourage people to migrate to the much less mistake-prone "error" setting. Update the plpgsql documentation to match this and other recent changes.
-
由 Heikki Linnakangas 提交于
but the transformed ArrayExpr claimed to have a return type of "domain", even though the domain constraint was only checked by the enclosing CoerceToDomain node. With this fix, the ArrayExpr is correctly labeled with the base type of the domain. Per gripe by Tom Lane.
-
由 Heikki Linnakangas 提交于
we need to check domain constraints. We used to do it correctly, but 8.4 introduced a separate code path for the "ARRAY[]::arraytype" case to infer the type of an empty ARRAY construct from the cast target, and forgot to take domains into account. Per report from Florian G. Pflug.
-
- 13 11月, 2009 2 次提交
-
-
由 Teodor Sigaev 提交于
User-defined consistent functions believes the check array contains at least one true element which was not a true for scanning pending list. Per report from Yury Don <yura@vpcit.ru>
-
由 Tom Lane 提交于
if the initial value of a string variable was NULL, which is entirely possible. Noted while experimenting with custom_variable_classes.
-
- 12 11月, 2009 8 次提交
-
-
由 Tom Lane 提交于
will work. Per buildfarm results.
-
由 Tom Lane 提交于
Per discussion, this should result in defaulting to SQL_ASCII encoding. The original coding could not support that because it conflated selection of SQL_ASCII encoding with not being able to determine the encoding. Adjust pg_get_encoding_from_locale()'s API to distinguish these cases, and fix callers appropriately. Only initdb actually changes behavior, since the other callers were perfectly content to consider these cases equivalent. Per bug #5178 from Boh Yap. Not going to bother back-patching, since no one has complained before and there's an easy workaround (namely, specify the encoding you want).
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
directly. This was a lot of trouble, but should be worth it in terms of not having to keep the plpgsql lexer in step with core anymore. In addition the handling of keywords is significantly better-structured, allowing us to de-reserve a number of words that plpgsql formerly treated as reserved.
-
由 Peter Eisentraut 提交于
for an arguably more pleasant display.
-
由 Alvaro Herrera 提交于
This is a preparatory patch for allowing a dynamic cursor name be used in the ECPG grammar. Author: Zoltan Boszormenyi
-
由 Alvaro Herrera 提交于
-
由 Alvaro Herrera 提交于
The main motivation for this is that it's required for Informix compatibility in ECPG. This patch makes the ECPG and core grammars a bit closer to one another for these productions. Author: Zoltan Boszormenyi
-