- 24 3月, 2007 2 次提交
-
-
由 Tom Lane 提交于
to the left of the actual bool value. While in most cases there won't be any, our support for old-style user-defined functions violates the C spec to the extent of calling functions that might return char or short through a function pointer declared to return "char *", which we then coerce to Datum. It is not surprising that the result might contain garbage high-order bits ... what is surprising is that we didn't see such cases long ago. Per report from Magnus.
-
由 Tom Lane 提交于
search_path that was active when the plan was first made. To do this, improve namespace.c to support a stack of "override" search path settings (we must have a stack since nested replan events are entirely possible). This facility replaces the "special namespace" hack formerly used by CREATE SCHEMA, and should be able to support per-function search path settings as well.
-
- 23 3月, 2007 18 次提交
-
-
由 Tatsuo Ishii 提交于
This is necessary to support JIS X 0213 <--> UTF-8 conversion.
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
stripped down version of libpq. To be used by the installer.
-
由 Magnus Hagander 提交于
Also remove headers for old sysv semaphore emulation that were forgotten when that was changed about a year ago.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> > * Fix cases where invalid byte encodings are accepted by the database, > but throw an error on SELECT > > http://archives.postgresql.org/pgsql-hackers/2007-03/msg00767.php
-
由 Bruce Momjian 提交于
Dave Page.
-
由 Bruce Momjian 提交于
CLUSTER: > > o %Add VERBOSE option to report tables as they are processed, > like VACUUM VERBOSE
-
由 Bruce Momjian 提交于
Nikolay Samokhvalov
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Nikolay Samokhvalov
-
由 Tom Lane 提交于
of a multi-statement simple-Query message. This bug goes all the way back, but unfortunately is not nearly so easy to fix in existing releases; it is only the recent ProcessUtility API change that makes it fixable in HEAD. Per report from William Garrison.
-
由 Bruce Momjian 提交于
SIGQUIT signal, rather than waiting for PGSTAT_RESTART_INTERVAL.
-
由 Tom Lane 提交于
doesn't exist. This allows DROP to be used to clean out the pg_tablespace catalog entry in a situation where a previous DROP attempt failed before committing but after having removed the directories and symlink. Per report from William Garrison. Even though his test case depends on an unrelated bug in PreventTransactionChain, it's certainly possible for this situation to arise due to other problems, eg a system crash at just the right time.
-
由 Bruce Momjian 提交于
full words support, per report from Mark Stosberg.
-
由 Alvaro Herrera 提交于
of palloc instead of malloc, which means a list can be freed simply by deleting the memory context that contains it.
-
- 22 3月, 2007 10 次提交
-
-
由 Teodor Sigaev 提交于
sizeof(wchar_t) = 2 instead of 4.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Magnus Hagander 提交于
-
由 Tom Lane 提交于
First, genericcostestimate() was being way too liberal about including partial-index conditions in its selectivity estimate, resulting in substantial underestimates for situations such as an indexqual "x = 42" used with an index on x "WHERE x >= 40 AND x < 50". While the code is intentionally set up to favor selecting partial indexes when available, this was too much... Second, choose_bitmap_and() was likewise easily fooled by cases of this type, since it would similarly think that the partial index had selectivity independent of the indexqual. Fixed by using predicate_implied_by() rather than simple equality checks to determine redundancy. This is a good deal more expensive but I don't see much alternative. At least the extra cost is only paid when there's actually a partial index under consideration. Per report from Jeff Davis. I'm not going to risk back-patching this, though.
-
由 Bruce Momjian 提交于
< < > o During index creation, pre-sort the tuples to improve build speed > > http://archives.postgresql.org/pgsql-hackers/2007-03/msg01199.php >
-
由 Bruce Momjian 提交于
< * Add NUMERIC division operator that doesn't round? < < Currently NUMERIC _rounds_ the result to the specified precision. < This means division can return a result that multiplied by the < divisor is greater than the dividend, e.g. this returns a value > 10: < < SELECT (10::numeric(2,0) / 6::numeric(2,0))::numeric(2,0) * 6; < < The positive modulus result returned by NUMERICs might be considered < inaccurate, in one sense. <
-
由 Magnus Hagander 提交于
-
由 Bruce Momjian 提交于
* Add locale-aware MONEY type, and support multiple currencies http://archives.postgresql.org/pgsql-hackers/2007-03/msg01181.php
-
由 Magnus Hagander 提交于
-
- 21 3月, 2007 6 次提交
-
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
Uses same underlying tech as before, but not the sysv emulation layer.
-
由 Bruce Momjian 提交于
* Allow accurate statistics to be collected on indexes with more than one column or expression indexes, perhaps using per-index statistics > http://archives.postgresql.org/pgsql-hackers/2007-03/msg01131.php
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
< o -Allow commenting of variables in postgresql.conf to restore them > o Allow commenting of variables in postgresql.conf to restore them
-
由 Bruce Momjian 提交于
> o -Allow commenting of variables in postgresql.conf to restore them < http://archives.postgresql.org/pgsql-hackers/2006-09/msg01481.php
-
- 20 3月, 2007 4 次提交
-
-
由 Neil Conway 提交于
and regexp_split_to_table. These functions provide access to the capture groups resulting from a POSIX regular expression match, and provide the ability to split a string on a POSIX regular expression, respectively. Patch from Jeremy Drake; code review by Neil Conway, additional comments and suggestions from Tom and Peter E. This patch bumps the catversion, adds some regression tests, and updates the docs.
-
由 Jan Wieck 提交于
BTW, the comment in this file says that we hope we never have more than 10 catversion changes per day, but to even make this possible we should start counting at zero, shouldn't we? Jan
-
由 Jan Wieck 提交于
rules to be defined with different, per session controllable, behaviors for replication purposes. This will allow replication systems like Slony-I and, as has been stated on pgsql-hackers, other products to control the firing mechanism of triggers and rewrite rules without modifying the system catalog directly. The firing mechanisms are controlled by a new superuser-only GUC variable, session_replication_role, together with a change to pg_trigger.tgenabled and a new column pg_rewrite.ev_enabled. Both columns are a single char data type now (tgenabled was a bool before). The possible values in these attributes are: 'O' - Trigger/Rule fires when session_replication_role is "origin" (default) or "local". This is the default behavior. 'D' - Trigger/Rule is disabled and fires never 'A' - Trigger/Rule fires always regardless of the setting of session_replication_role 'R' - Trigger/Rule fires when session_replication_role is "replica" The GUC variable can only be changed as long as the system does not have any cached query plans. This will prevent changing the session role and accidentally executing stored procedures or functions that have plans cached that expand to the wrong query set due to differences in the rule firing semantics. The SQL syntax for changing a triggers/rules firing semantics is ALTER TABLE <tabname> <when> TRIGGER|RULE <name>; <when> ::= ENABLE | ENABLE ALWAYS | ENABLE REPLICA | DISABLE psql's \d command as well as pg_dump are extended in a backward compatible fashion. Jan
-
由 Bruce Momjian 提交于
"If the patch is not BSD-licensed, it will be rejected."
-