- 28 8月, 2007 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
corrections. Not sure why these were not in CVS. Researching.
-
由 Bruce Momjian 提交于
fixes. Not sure how these weren't comitted before.
-
- 27 8月, 2007 13 次提交
-
-
由 Magnus Hagander 提交于
pending decision on exactly what will happen with contrib/tsearch2 now that it's in core.
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
-
由 Tom Lane 提交于
namespace isn't necessarily first in the search path (there could be implicit schemas ahead of it). Examples are test=# set search_path TO s1; test=# create view pg_timezone_names as select * from pg_timezone_names(); ERROR: "pg_timezone_names" is already a view test=# create table pg_class (f1 int primary key); ERROR: permission denied: "pg_class" is a system catalog You'd expect these commands to create the requested objects in s1, since names beginning with pg_ aren't supposed to be reserved anymore. What is happening is that we create the requested base table and then execute additional commands (here, CREATE RULE or CREATE INDEX), and that code is passed the same RangeVar that was in the original command. Since that RangeVar has schemaname = NULL, the secondary commands think they should do a path search, and that means they find system catalogs that are implicitly in front of s1 in the search path. This is perilously close to being a security hole: if the secondary command failed to apply a permission check then it'd be possible for unprivileged users to make schema modifications to system catalogs. But as far as I can find, there is no code path in which a check doesn't occur. Which makes it just a weird corner-case bug for people who are silly enough to want to name their tables the same as a system catalog. The relevant code has changed quite a bit since 8.2, which means this patch wouldn't work as-is in the back branches. Since it's a corner case no one has reported from the field, I'm not going to bother trying to back-patch.
-
由 Tom Lane 提交于
days that was obsolete the moment we had IN (SELECT ...) capability. It's arguably a security hole since it applied no permissions check to the table it searched, and since it was never documented anywhere, removing it seems more appropriate than fixing it.
-
由 Tom Lane 提交于
not all that exciting when the system catalogs are readable by all, but some people try to lock them down, and would not like this sort of end run ...
-
由 Tom Lane 提交于
and pg_tablespace_size to superusers. Perhaps we could weaken the first case to just require SELECT privilege, but that doesn't work for the other cases, so use ownership as the common concept.
-
由 Tom Lane 提交于
While it's not clear that TID linkage info is of any great use to a nefarious user, it's certainly unexpected that these functions wouldn't insist on read privileges.
-
由 Tom Lane 提交于
but no permissions check at all is certainly no good.) Clean up usage of some deprecated APIs.
-
由 Tom Lane 提交于
but no permissions check at all is certainly no good.) Clean up usage of some deprecated APIs.
-
由 Tom Lane 提交于
usage of RelationNameGetTupleDesc().
-
由 Tom Lane 提交于
exposing user data to others, and clean up usage of deprecated APIs.
-
由 Tom Lane 提交于
sub-select returns zero rows. Per complaint from Jens Schicke. Since this is more in the nature of a definition change than a bug, not back-patched.
-
- 26 8月, 2007 3 次提交
-
-
由 Tom Lane 提交于
but just hardwire the specified timezone database path into the executable. Per discussion, this avoids some packaging disadvantages of using a symlink.
-
由 Tom Lane 提交于
relcache entry after having heap_close'd it. This could lead to misbehavior if a relcache flush wiped out the cache entry meanwhile. In 8.2 there is a very real risk of CREATE INDEX CONCURRENTLY using the wrong relid for locking and waiting purposes. I think the bug is only cosmetic in 8.0 and 8.1, because their transgression is limited to using RelationGetRelationName(rel) in an ereport message immediately after heap_close, and there's no way (except with special debugging options) for a cache flush to occur in that interval. Not quite sure that it's cosmetic in 7.4, but seems best to patch anyway. Found by trying to run the regression tests with CLOBBER_CACHE_ALWAYS enabled. Maybe we should try to do that on a regular basis --- it's awfully slow, but perhaps some fast buildfarm machine could do it once in awhile.
-
由 Tom Lane 提交于
of redundant sub-selects. initdb not forced, since this is just a cosmetic change, but the new code won't show up till you do one.
-
- 25 8月, 2007 5 次提交
-
-
由 Tatsuo Ishii 提交于
(FD_SETSIZE - 10) rather than a hardwired number.
-
由 Tom Lane 提交于
minor rewording, some markup fixups. Lots left to do here ...
-
由 Tom Lane 提交于
Minor other cleanups.
-
由 Tom Lane 提交于
russian_stem, etc. Per discussion.
-
由 Tom Lane 提交于
- ispell initialization crashed on empty dictionary file - ispell initialization crashed on affix file with prefixes but no suffixes - stop words file was run through pg_verify_mbstr, with database encoding, but it's supposed to be UTF-8; similar bug for synonym files - bunch of comments added, typos fixed, and other cleanup Introduced consistent encoding checking/conversion of data read from tsearch configuration files, by doing this in a single t_readline() subroutine (replacing direct usages of fgets). Cleaned up API for readstopwords too. Heikki Linnakangas
-
- 24 8月, 2007 1 次提交
-
-
由 Tom Lane 提交于
padded encryption scheme. Formerly it would try to access res[(unsigned) -1], which resulted in core dumps on 64-bit machines, and was certainly trouble waiting to happen on 32-bit machines (though in at least the known case it was harmless because that byte would be overwritten after return). Per report from Ken Colson; fix by Marko Kreen.
-
- 23 8月, 2007 6 次提交
-
-
由 Andrew Dunstan 提交于
the same amount of memory in ErrorContext as standard logs.
-
由 Andrew Dunstan 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Transactional Information Systems by Gerhard Weikum, Kaufmann
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
initdb. We should create all the standard dictionaries even though some of them may not work in template1's encoding. Per Teodor.
-
- 22 8月, 2007 8 次提交
-
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
This prevents needing to do complex and poorly-defined updates of the mapping table if the new parser has different token types than the old. Per discussion.
-
由 Tom Lane 提交于
syncing the existing docs with the final syntax decisions.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
names in the former case seems more consistent with the behavior of other \dF commands.
-