- 22 3月, 2007 1 次提交
-
-
由 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 6 次提交
-
-
由 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."
-
由 Tom Lane 提交于
test in parallel with the rules test at all, because the former wants to create a couple of temp views, which can sometimes show up in the latter's output. Let's try it in the next parallel group instead.
-
由 Tom Lane 提交于
to cover it. Per report from Anton Pikhteryev.
-
- 19 3月, 2007 5 次提交
-
-
由 Bruce Momjian 提交于
* Simplify ability to create partitioned tables > http://archives.postgresql.org/pgsql-hackers/2007-03/msg00375.php
-
由 Bruce Momjian 提交于
* Allow sequential scans to take advantage of other concurrent sequential scans, also called "Synchronised Scanning" http://archives.postgresql.org/pgsql-hackers/2007-03/msg00415.php
-
由 Magnus Hagander 提交于
-
由 Tom Lane 提交于
on preproc.h, else make may try to build it before preproc.h is ready. Per failures seen here and in buildfarm.
-
由 Neil Conway 提交于
are initialized with a string literal. Patch from Stefan Huehner.
-
- 18 3月, 2007 4 次提交
-
-
由 Neil Conway 提交于
to ANSI-style, and change "()" -> "(void)". Patch from Stefan Huehner.
-
由 Michael Meskes 提交于
-
由 Michael Meskes 提交于
- Made some chars const as proposed by Stefan Huehner <stefan@huehner.org>. - Synced parser and keyword lists. - Copied two token parsing from backend parser to ecpg parser. - Also added a test case for this.
-
由 Magnus Hagander 提交于
-
- 17 3月, 2007 9 次提交
-
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
what each script does.
-
由 Magnus Hagander 提交于
-
由 Magnus Hagander 提交于
skeleton scripts calling them. To make it easier for the buildfarm (or other "outside callers") to use these modules directly. Per suggestion from Andrew Dunstan.
-
由 Tom Lane 提交于
executed in read_only mode. This could lead to various relatively-subtle failures, such as an allegedly stable function returning non-stable results. Bug goes all the way back to the introduction of read-only mode in 8.0. Per report from Gaetano Mendola.
-
由 Tom Lane 提交于
cut at exprTypmod support. Also, experimentation shows that we need to label the type of Const nodes that are numeric with a specific typmod.
-
由 Tom Lane 提交于
available information about the typmod of an expression; namely, Const, ArrayRef, ArrayExpr, and EXPR and ARRAY SubLinks. In the ArrayExpr and SubLink cases it wasn't really the data structure's fault, but exprTypmod() being lazy. This seems like a good idea in view of the expected increase in typmod usage from Teodor's work to allow user-defined types to have typmods. In particular this responds to the concerns we had about eliminating the special-purpose hack that exprTypmod() used to have for BPCHAR Consts. We can now tell whether or not such a Const has been cast to a specific length, and report or display properly if so. initdb forced due to changes in stored rules.
-
由 Magnus Hagander 提交于
pg_stat_database.
-
由 Tom Lane 提交于
was expecting there to be no regular table named 'foo', but it turns out the rules test transiently creates one, so that plancache would sometimes fail. I couldn't reproduce that in quite a few tries here, but several buildfarm machines have shown the failure. Fix by renaming plancache's temp table to something nonconflicting.
-
- 16 3月, 2007 4 次提交
-
-
由 Alvaro Herrera 提交于
reported in some cases. Report and patch from Tatsuhito Kasahara. Also fix a couple of other bugs I noticed in skimming the surrounding code.
-
由 Andrew Dunstan 提交于
Remove undocumented support for copy syntax from before 7.3. Update comments to reflect syntax actually supported, e.g. by including CSV params.
-
由 Magnus Hagander 提交于
Greg Sabino Mullane
-
由 Tom Lane 提交于
uses SPI plans, this finally fixes the ancient gotcha that you can't drop and recreate a temp table used by a plpgsql function. Along the way, clean up SPI's API a little bit by declaring SPI plan pointers as "SPIPlanPtr" instead of "void *". This is cosmetic but helps to forestall simple programming mistakes. (I have changed some but not all of the callers to match; there are still some "void *"'s in contrib and the PL's. This is intentional so that we can see if anyone's compiler complains about it.)
-
- 15 3月, 2007 2 次提交
-
-
由 Tom Lane 提交于
did not expect that a DEAD tuple could follow a RECENTLY_DEAD tuple in an update chain, but because the OldestXmin rule for determining deadness is a simplification of reality, it is possible for this situation to occur (implying that the RECENTLY_DEAD tuple is in fact dead to all observers, but this patch does not attempt to exploit that). The code would follow a chain forward all the way, but then stop before a DEAD tuple when backing up, meaning that not all of the chain got moved. This could lead to copying the chain multiple times (resulting in duplicate copies of the live tuple at its end), or leaving dangling index entries behind (which, aside from generating warnings from later vacuums, creates a risk of wrong query results or bogus duplicate-key errors once the heap slot the index entry points to is repopulated). The fix is to recheck HeapTupleSatisfiesVacuum while following a chain forward, and to stop if a DEAD tuple is reached. Each contiguous group of RECENTLY_DEAD tuples will therefore be copied as a separate chain. The patch also adds a couple of extra sanity checks to verify correct behavior. Per report and test case from Pavan Deolasee.
-
由 Tom Lane 提交于
POSIX-style timezone specs that don't exactly match any database entry will be treated as having correct USA DST rules. Also, document that this can be changed if you want to use some other DST rules with a POSIX zone spec. We could consider changing localtime.c's TZDEFRULESTRING, but since that facility can only deal with one DST transition rule, it seems fairly useless now; might as well just plan to override it using a "posixrules" entry. Backpatch as far as 8.0. There isn't much we can do in 7.x ... either your libc gets it right, or it doesn't.
-
- 14 3月, 2007 3 次提交
-
-
由 Teodor Sigaev 提交于
with minor editorization by me. Hstore improvements * add operation hstore ? text - excat equivalent of exist() * remove undocumented behaviour of contains operation with NULL value * now 'key'::text=>NULL returns '"key"=>NULL' instead of NULL * Add GIN support for contains and exist operations * Add GiST support for exist operatiion * improve regression tests
-
由 Teodor Sigaev 提交于
with minor editorization by me.
-
由 Magnus Hagander 提交于
single quotes...
-