- 29 7月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
materialized. New items have been added to GucContext and GucSource enums, but of course they were not added to the corresponding GucContextName[] and GucSourceName[] arrays in the patch. Here's a new patch to fix the resulting bugs. Joe Conway
-
- 28 7月, 2003 2 次提交
- 27 7月, 2003 2 次提交
-
-
由 Tom Lane 提交于
the bulk of the heavy lifting ...
-
由 Bruce Momjian 提交于
>>ISTM that "source" is worth knowing. > > Hm, possibly. Any other opinions? This version has the seven fields I proposed, including "source". Here's an example that shows why I think it's valuable: regression=# \x Expanded display is on. regression=# select * from pg_settings where name = 'enable_seqscan'; -[ RECORD 1 ]----------- name | enable_seqscan setting | on context | user vartype | bool source | default min_val | max_val | regression=# update pg_settings set setting = 'off' where name = 'enable_seqscan'; -[ RECORD 1 ]--- set_config | off regression=# select * from pg_settings where name = 'enable_seqscan'; -[ RECORD 1 ]----------- name | enable_seqscan setting | off context | user vartype | bool source | session min_val | max_val | regression=# alter user postgres set enable_seqscan to 'off'; ALTER USER (log out and then back in again) regression=# \x Expanded display is on. regression=# select * from pg_settings where name = 'enable_seqscan'; -[ RECORD 1 ]----------- name | enable_seqscan setting | off context | user vartype | bool source | user min_val | max_val | In the first case, enable_seqscan is set to its default value. After setting it to off, it is obvious that the value has been changed for the session only. In the third case, you can see that the value has been set specifically for the user. Joe Conway
-
- 26 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 25 7月, 2003 2 次提交
- 23 7月, 2003 2 次提交
- 22 7月, 2003 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
- 21 7月, 2003 2 次提交
- 20 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 19 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
-
- 18 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
date2j(). This ensures we give reasonable errors instead of bizarre behavior for input dates far in the future.
-
- 17 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
for the sign of timezone offsets, ie, positive is east from UTC. These were previously out of step with other operations that accept or show timezones, such as I/O of timestamptz values.
-
- 15 7月, 2003 3 次提交
- 10 7月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Aizaz Ahmed
-
- 09 7月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
or increased only by super-users. This fixes problems caused by making certain variables SUSET for security reasons.
-
- 05 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
without needing a running backend. Reorder postgresql.conf.sample to match new layout of runtime.sgml. This commit re-adds work lost in Wednesday's crash.
-
- 04 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
function-not-found messages now distinguish the cases no-match and ambiguous-match, and they follow the style guidelines too.
-
- 02 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
It also works to create a non-polymorphic aggregate from polymorphic functions, should you want to do that. Regression test added, docs still lacking. By Joe Conway, with some kibitzing from Tom Lane.
-
- 01 7月, 2003 1 次提交
-
-
由 Tom Lane 提交于
reports get put into the postmaster log. Options are TERSE, DEFAULT, VERBOSE, with the same behavior as implemented on the client side in libpq.
-
- 27 6月, 2003 2 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
comparison functions), replacing the highly bogus bitwise array_eq. Create a btree index opclass for ANYARRAY --- it is now possible to create indexes on array columns. Arrange to cache the results of catalog lookups across multiple array operations, instead of repeating the lookups on every call. Add string_to_array and array_to_string functions. Remove singleton_array, array_accum, array_assign, and array_subscript functions, since these were for proof-of-concept and not intended to become supported functions. Minor adjustments to behavior in some corner cases with empty or zero-dimensional arrays. Joe Conway (with some editorializing by Tom Lane).
-
- 26 6月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Joe Conway
-
- 25 6月, 2003 3 次提交
-
-
由 Bruce Momjian 提交于
pg_get_constraintdef() for >= 70400. Rod Taylor <rbt@rbt.ca>
-
由 Bruce Momjian 提交于
Joe Conway
-
由 Bruce Momjian 提交于
Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
-
- 23 6月, 2003 1 次提交
-
-
由 Tom Lane 提交于
specific hash functions used by hash indexes, rather than the old not-datatype-aware ComputeHashFunc routine. This makes it safe to do hash joining on several datatypes that previously couldn't use hashing. The sets of datatypes that are hash indexable and hash joinable are now exactly the same, whereas before each had some that weren't in the other.
-
- 12 6月, 2003 2 次提交
-
-
由 Bruce Momjian 提交于
free'd for every transaction or statement, respectively. This patch puts these data structures into static memory, thus saving a few CPU cycles and two malloc calls per transaction or (in isolation level READ COMMITTED) per query. Manfred Koizar
-
由 Bruce Momjian 提交于
Christopher Kings-Lynne
-
- 11 6月, 2003 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 29 5月, 2003 1 次提交
-
-
由 Tom Lane 提交于
of an index can now be a computed expression instead of a simple variable. Restrictions on expressions are the same as for predicates (only immutable functions, no sub-selects). This fixes problems recently introduced with inlining SQL functions, because the inlining transformation is applied to both expression trees so the planner can still match them up. Along the way, improve efficiency of handling index predicates (both predicates and index expressions are now cached by the relcache) and fix 7.3 oversight that didn't record dependencies of predicate expressions.
-
- 28 5月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
docs that CLIENT/LOG_MIN_MESSAGES now controls debug_* output location. Doc changes included.
-