- 30 11月, 2009 7 次提交
-
-
由 Peter Eisentraut 提交于
branch, which is how most actual code is actually structured. Also fix slight whitespace misalignment.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
we have to tell Perl it can release its compiled copy of the function text. Noted by Alexey Klyukin. Back-patch to 8.2 --- the problem exists further back, but this patch won't work without modification, and it's probably not worth the trouble.
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
arrays in a pg_proc entry match. Seems like an easy mistake to make when manually adjusting these values in a pg_proc.h entry.
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
being hidden when current_query is. Relocate it to a column position more consistent with that behavior. Per discussion.
-
- 29 11月, 2009 3 次提交
-
-
由 Tom Lane 提交于
Joshua Tolley, reviewed by Brendan Jurd and Tim Bunce
-
由 Tom Lane 提交于
pg_stat_activity and recorded in log entries. Dave Page, reviewed by Andres Freund
-
由 Bruce Momjian 提交于
Add link to exteran fsync testing script and our fsync test tool.
-
- 28 11月, 2009 4 次提交
-
-
由 Bruce Momjian 提交于
Improve test descriptions displayed during test_fsync; increase default loops to 5k.
-
由 Tom Lane 提交于
by adding a requirement that build_join_rel add new join RelOptInfos to the appropriate list immediately at creation. Per report from Robert Haas, the list_concat_unique_ptr() calls that this change eliminates were taking the lion's share of the runtime in larger join problems. This doesn't do anything to fix the fundamental combinatorial explosion in large join problems, but it should push out the threshold of pain a bit further. Note: because this changes the order in which joinrel lists are built, it might result in changes in selected plans in cases where different alternatives have exactly the same costs. There is one example in the regression tests.
-
由 Bruce Momjian 提交于
vacuum.
-
由 Michael Meskes 提交于
comment.
-
- 27 11月, 2009 3 次提交
-
-
由 Michael Meskes 提交于
string too.
-
由 Michael Meskes 提交于
in the build process. If not the build process will stop with an error message.
-
由 Tom Lane 提交于
-
- 26 11月, 2009 5 次提交
-
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
Boszormenyi Zoltan, with only a minor tweak or two from me.
-
由 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
-