- 01 2月, 2007 16 次提交
-
-
由 Bruce Momjian 提交于
> > * Tighten function permission checks > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php >
-
由 Bruce Momjian 提交于
> > * Tighten trigger permission checks > > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php >
-
由 Neil Conway 提交于
and --password for pg_dump, pg_dumpall and pg_restore, per complaint by Michael Schmidt. Patch from Magnus Hagander.
-
由 Bruce Momjian 提交于
> > * Fix problem when multiple subtransactions of the same outer transaction > hold different types of locks, and one subtransaction aborts > > http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php > http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php
-
由 Neil Conway 提交于
-
由 Bruce Momjian 提交于
created and increments. The old docs created the sequence, then showed a nextval() of 114.
-
由 Bruce Momjian 提交于
o Fix RENAME to work on variables other than OLD/NEW > http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php
-
由 Bruce Momjian 提交于
appropriate.
-
由 Bruce Momjian 提交于
Standard English uses "may", "can", and "might" in different ways: may - permission, "You may borrow my rake." can - ability, "I can lift that log." might - possibility, "It might rain today." Unfortunately, in conversational English, their use is often mixed, as in, "You may use this variable to do X", when in fact, "can" is a better choice. Similarly, "It may crash" is better stated, "It might crash".
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Standard English uses "may", "can", and "might" in different ways: may - permission, "You may borrow my rake." can - ability, "I can lift that log." might - possibility, "It might rain today." Unfortunately, in conversational English, their use is often mixed, as in, "You may use this variable to do X", when in fact, "can" is a better choice. Similarly, "It may crash" is better stated, "It might crash". Also update two error messages mentioned in the documenation to match.
-
由 Neil Conway 提交于
targets, and refactor the tablespace setup code into a separate Makefile target.
-
由 Neil Conway 提交于
nonportable "hh" sprintf(3) length modifier. Instead, do the parsing and output by hand. The code to do this isn't ideal, but this is an interim measure anyway: the uuid type should probably use the in-memory struct layout specified by RFC 4122. For now, this patch should hopefully rectify the buildfarm failures for the uuid test. Along the way, re-add pg_cast entries for uuid <-> varchar, which I mistakenly removed earlier, and bump the catversion.
-
由 Tom Lane 提交于
or other share-directory files are inaccessible for some reason other than not existing. Inspired by trouble report from Simon Kinsella.
-
由 Teodor Sigaev 提交于
-
- 31 1月, 2007 12 次提交
-
-
由 Teodor Sigaev 提交于
-
由 Teodor Sigaev 提交于
In this case extractQuery should returns -1 as nentries. This changes prototype of extractQuery method to use int32* instead of uint32* for nentries argument. Based on that gincostestimate may see two corner cases: nothing will be found or seqscan should be used. Per proposal at http://archives.postgresql.org/pgsql-hackers/2007-01/msg01581.php PS tsearch_core patch should be sightly modified to support changes, but I'm waiting a verdict about reviewing of tsearch_core patch.
-
由 Bruce Momjian 提交于
o Fix RENAME to work on variables other than OLD/NEW > > http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php >
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> > * Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY > > This is difficult because you must upgrade to an exclusive table lock > to replace the existing index file. CREATE INDEX CONCURRENTLY does not > have this complication. This would allow index compaction without > downtime.
-
由 Bruce Momjian 提交于
< reindex rather than update the index. > reindex rather than update the index. Also, index updates can > bloat the index.
-
由 Bruce Momjian 提交于
> o ARRAY[[1,2],[3,4]])[1] should return the same values as > ARRAY[[1,2],[3,4]])[1:1]; >
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
more, and standard_conforming_strings less, because in the future non-E strings will not treat backslashes specially. Also use E'' strings where backslashes are used in examples. (The existing examples would have drawn warnings.) Backpatch to 8.2.X.
-
由 Tom Lane 提交于
The original coding failed (tried to access deallocated memory) if there were two active call sites (fn_extra pointers) for the same function and the function definition was updated. Also, if an update of a recursive function was detected upon nested entry to the function, the existing compiled version was summarily deallocated, resulting in crash upon return to the outer instance. Problem observed while studying a bug report from Sergiy Vyshnevetskiy. Bug does not exist before 8.1 since older versions just leaked the memory of obsoleted compiled functions, rather than trying to reclaim it.
-
由 Tom Lane 提交于
by plpgsql can themselves use SPI --- possibly indirectly, as in the case of domain_in() invoking plpgsql functions in a domain check constraint. Per bug #2945 from Sergiy Vyshnevetskiy. Somewhat arbitrarily, I've chosen to back-patch this as far as 8.0. Given the lack of prior complaints, it doesn't seem critical for 7.x.
-
- 30 1月, 2007 7 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
Hashing for aggregation purposes still needs work, so it's not time to mark any cross-type operators as hashable for general use, but these cases work if the operators are so marked by hand in the system catalogs.
-
由 Tom Lane 提交于
actually used for anything.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< * Add Globally/Universally Unique Identifier (GUID/UUID) > * -Add Globally/Universally Unique Identifier (GUID/UUID)
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
from exec.c and postmaster.c.
-
- 29 1月, 2007 5 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
match because they contain a null join key (and the join operator is known strict). Improves performance significantly when the inner relation contains a lot of nulls, as per bug #2930.
-
由 Tom Lane 提交于
handy to prevent core dump files from disappearing, but it's useless now because (a) we don't drop core in individual DB subdirectories anymore, and (b) CREATE DATABASE forces an internal checkpoint anyway.
-
由 Neil Conway 提交于
definitions of uuid_t that may be provided by the system headers. This should hopefully fix the Win32 build problems reported by Magnus.
-
由 Andrew Dunstan 提交于
-