- 28 6月, 2011 3 次提交
-
-
由 Simon Riggs 提交于
WAL records of type XLOG_BTREE_REUSE_PAGE were generated using a latestRemovedXid one higher than actually needed because xid used was page opaque->btpo.xact rather than an actually removed xid. Noticed on an otherwise quiet system by Noah Misch. Noah Misch and Simon Riggs
-
由 Robert Haas 提交于
Since the names try_relation_openrv() and try_heap_openrv() don't seem quite appropriate, rename the functions to relation_openrv_extended() and heap_openrv_extended(). This is also more general, if we have a future need for additional parameters that are of interest to only a few callers. This is infrastructure for a forthcoming patch to allow get_object_address() to take a missing_ok argument as well. Patch by me, review by Noah Misch.
-
由 Robert Haas 提交于
My previous attempt was quite a bit less than half-baked with respect to heap_update().
-
- 27 6月, 2011 10 次提交
-
-
由 Robert Haas 提交于
As noted by Christian Ullrich.
-
由 Robert Haas 提交于
It's been like this since HOT was originally introduced, but the logic is complex enough that this is a recipe for bugs, as we've already found out with SSI. So refactor heap_hot_search_buffer() so that it can satisfy the needs of index_getnext(), and make index_getnext() use that rather than duplicating the logic. This change was originally proposed by Heikki Linnakangas as part of a larger refactoring oriented towards allowing index-only scans. I extracted and adjusted this part, since it seems to have independent merit. Review by Jeff Davis.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
DEF_PGPORT already comes in from pg_config.h, so we don't need to pass it in again with a -D option. Apparently a leftover from the shell script conversion.
-
由 Peter Eisentraut 提交于
This doesn't actually change the resulting set of strings, but better be correct.
-
由 Peter Eisentraut 提交于
The --flag argument can be used to tell xgettext the arguments of which functions should be flagged with c-format in the PO files, instead of guessing based on the presence of format specifiers, which fails if no format specifiers are present but the translation accidentally introduces one. Appropriate flag settings have been added for each message catalog. based on a patch by Christoph Berg for bug #6066
-
由 Peter Eisentraut 提交于
Put gettext trigger words that are common to the backend and backend modules into a makefile variable to include everywhere, to avoid error-prone repetitions.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
Since it's globally defined in c.h, it should be treated as a gettext trigger everywhere.
-
由 Peter Eisentraut 提交于
It currently doesn't make a difference, but it's inconsistent with most other usage, and it might interfere with a future patch, so I'll change it all in a separate commit. Also, replace tabs with spaces for alignment.
-
- 26 6月, 2011 2 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Joe Conway 提交于
use DBLINK_GET_NAMED_CONN rather than DBLINK_GET_CONN. Problem found by Peter Eisentraut and patch by Fujii Masao.
-
- 25 6月, 2011 1 次提交
-
-
由 Robert Haas 提交于
Explain that querying pg_locks does not simultaneously lock both the normal lock manager and the predicate lock manager. Per discussion with Kevin Grittner.
-
- 24 6月, 2011 2 次提交
-
-
由 Bruce Momjian 提交于
Backpatch to 9.1 and 9.0.
-
由 Peter Eisentraut 提交于
-
- 23 6月, 2011 11 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
s/const//g wasn't exactly what I was suggesting here ... parameter declarations of the form "const structtype *param" are good and useful, so put those occurrences back. Likewise, avoid casting away the const in a "const void *" parameter.
-
由 Bruce Momjian 提交于
major version. Backpatch to 9.1. Dan McGee
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
binary directory has been validated. Backpatch to 9.1. Dan McGee
-
由 Bruce Momjian 提交于
Backpatch to 9.1 and 9.0. Dan McGee
-
由 Tom Lane 提交于
Per bug #6073 from Hartmut Raschick.
-
由 Tom Lane 提交于
backend/Makefile was treating errcodes.h as a header always generated during build, but actually it's a header provided in tarballs. Hence, must use the absolute-symlink recipe, not the relative-symlink one. Per bug #6072 from Hartmut Raschick.
-
- 22 6月, 2011 11 次提交
-
-
由 Robert Haas 提交于
It's not entirely stable. Per suggestion from Josh Kupershmidt.
-
由 Heikki Linnakangas 提交于
As Tom Lane pointed out, "const Relation foo" doesn't guarantee that you can't modify the data the "foo" pointer points to. It just means that you can't change the pointer to point to something else within the function, which is not very useful.
-
由 Robert Haas 提交于
This involves two main changes from the previous behavior. First, when we set a bit in the visibility map, emit a new WAL record of type XLOG_HEAP2_VISIBLE. Replay sets the page-level PD_ALL_VISIBLE bit and the visibility map bit. Second, when inserting, updating, or deleting a tuple, we can no longer get away with clearing the visibility map bit after releasing the lock on the corresponding heap page, because an intervening crash might leave the visibility map bit set and the page-level bit clear. Making this work requires a bit of interface refactoring. In passing, a few minor but related cleanups: change the test in visibilitymap_set and visibilitymap_clear to throw an error if the wrong page (or no page) is pinned, rather than silently doing nothing; this case should never occur. Also, remove duplicate definitions of InvalidXLogRecPtr. Patch by me, review by Noah Misch.
-
由 Robert Haas 提交于
Josh Kupershmidt
-
由 Robert Haas 提交于
This is just like serial and bigserial, except it generates an int2 column rather than int4 or int8. Mike Pultz, reviewed by Brar Piening and Josh Kupershmidt
-
由 Robert Haas 提交于
This allows deadlock_timeout to be reduced for transactions that are particularly likely to be involved in a deadlock, thus detecting it more quickly. It is also potentially useful as a poor-man's deadlock priority mechanism: a transaction with a high deadlock_timeout is less likely to be chosen as the victim than one with a low deadlock_timeout. Since that could be used to game the system, we make this PGC_SUSET rather than PGC_USERSET. At some point, it might be worth thinking about a more explicit priority mechanism, since using this is far from fool-proof. But let's see whether there's enough use case to justify the additional work before we go down that route. Noah Misch, reviewed by Shigeru Hanada
-
由 Robert Haas 提交于
Initially, we use this only to eliminate calls to the varchar() function in cases where the length is not being reduced and, therefore, the function call is equivalent to a RelabelType operation. The most significant effect of this is that we can avoid a table rewrite when changing a varchar(X) column to a varchar(Y) column, where Y > X. Noah Misch, reviewed by me and Alexey Klyukin
-
由 Robert Haas 提交于
Kevin Grittner, with additional wordsmithing by me.
-
由 Tom Lane 提交于
Fix some grammatical issues, try to clarify a couple of proofs, make the terminology more consistent.
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
A password containing a character with the high bit set was misprocessed on machines where char is signed (which is most). This could cause the preceding one to three characters to fail to affect the hashed result, thus weakening the password. The result was also unportable, and failed to match some other blowfish implementations such as OpenBSD's. Since the fix changes the output for such passwords, upstream chose to provide a compatibility hack: password salts beginning with $2x$ (instead of the usual $2a$ for blowfish) are intentionally processed "wrong" to give the same hash as before. Stored password hashes can thus be modified if necessary to still match, though it'd be better to change any affected passwords. In passing, sync a couple other upstream changes that marginally improve performance and/or tighten error checking. Back-patch to all supported branches. Since this issue is already public, no reason not to commit the fix ASAP.
-