- 14 1月, 2008 1 次提交
-
-
由 Tom Lane 提交于
command IDs.
-
- 04 12月, 2007 1 次提交
-
-
由 Tom Lane 提交于
-
- 03 12月, 2007 2 次提交
- 28 11月, 2007 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 21 6月, 2007 1 次提交
-
-
由 Tom Lane 提交于
constraints the planner is unable to disprove, hence simple btree-compatible conditions should be used. We've seen people try to get cute with stuff like date_part(something) = something at least twice now. Even if we wanted to try to teach predtest.c about the properties of date_part, most of the useful variants aren't immutable so nothing could be proved.
-
- 16 5月, 2007 1 次提交
-
-
由 Neil Conway 提交于
information" is un-good English.
-
- 03 5月, 2007 1 次提交
-
-
由 Neil Conway 提交于
the relevant fixes to 8.2 as well.
-
- 01 2月, 2007 2 次提交
-
-
由 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". Also update two error messages mentioned in the documenation to match.
-
- 31 12月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 29 12月, 2006 1 次提交
-
-
由 Tom Lane 提交于
for use with constraint exclusion. We can prove those cases now...
-
- 28 11月, 2006 1 次提交
-
-
由 Tom Lane 提交于
inherited, per Taiki Yamaguchi.
-
- 21 11月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
of caveats in different places, but close together. One called caveats, one not. That looks like it just led to somebody not reading some appropriate caveats in the second group of caveats (on -admin). Simon Riggs
-
- 24 10月, 2006 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 22 10月, 2006 1 次提交
-
-
由 Tom Lane 提交于
-
- 17 10月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
Update find_gt_lt to allow grep parameters to be passed into it.
-
- 14 10月, 2006 1 次提交
-
-
由 Tom Lane 提交于
-
- 21 9月, 2006 1 次提交
-
-
由 Tom Lane 提交于
-
- 20 9月, 2006 1 次提交
-
-
由 Neil Conway 提交于
Stark, additional fixes and editorialization by Neil Conway. Greg's patch description: Some more doc patches for partitioned tables. In particular replace the caveat that INCLUDING CONSTRAINTS doesn't exist and replace it with documentation of, well, INCLUDING CONSTRAINTS. Also, there was an instance of "LIKE WITH DEFAULTS" which is actually spelled "LIKE INCLUDING DEFAULTS".
-
- 06 9月, 2006 1 次提交
-
-
由 Tom Lane 提交于
can create or modify rules for the table. Do setRuleCheckAsUser() while loading rules into the relcache, rather than when defining a rule. This ensures that permission checks for tables referenced in a rule are done with respect to the current owner of the rule's table, whereas formerly ALTER TABLE OWNER would fail to update the permission checking for associated rules. Removal of separate RULE privilege is needed to prevent various scenarios in which a grantee of RULE privilege could effectively have any privilege of the table owner. For backwards compatibility, GRANT/REVOKE RULE is still accepted, but it doesn't do anything. Per discussion here: http://archives.postgresql.org/pgsql-hackers/2006-04/msg01138.php
-
- 14 7月, 2006 1 次提交
-
-
由 Neil Conway 提交于
-
- 04 7月, 2006 1 次提交
-
-
由 Tom Lane 提交于
-
- 02 7月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
Open items: There were a few tangentially related issues that have come up that I think are TODOs. I'm likely to tackle one or two of these next so I'm interested in hearing feedback on them as well. . Constraints currently do not know anything about inheritance. Tom suggested adding a coninhcount and conislocal like attributes have to track their inheritance status. . Foreign key constraints currently do not get copied to new children (and therefore my code doesn't verify them). I don't think it would be hard to add them and treat them like CHECK constraints. . No constraints at all are copied to tables defined with LIKE. That makes it hard to use LIKE to define new partitions. The standard defines LIKE and specifically says it does not copy constraints. But the standard already has an option called INCLUDING DEFAULTS; we could always define a non-standard extension LIKE table INCLUDING CONSTRAINTS that gives the user the option to request a copy including constraints. . Personally, I think the whole attislocal thing is bunk. The decision about whether to drop a column from children tables or not is something that should be up to the user and trying to DWIM based on whether there was ever a local definition or the column was acquired purely through inheritance is hardly ever going to match up with user expectations. . And of course there's the whole unique and primary key constraint issue. I think to get any traction at all on this you have a prerequisite of a real partitioned table implementation where the system knows what the partition key is so it can recognize when it's a leading part of an index key. Greg Stark
-
- 01 5月, 2006 1 次提交
-
-
由 Tom Lane 提交于
CONNECTION, fix a number of places that were missed (eg pg_dump support), avoid executing an extra search of pg_database during startup.
-
- 23 4月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
compatibility for release 7.2 and earlier. I have not altered any mentions of release 7.3 or later. The release notes were not modified, so the changes are still documented, just not in the main docs.
-
- 19 2月, 2006 1 次提交
-
-
由 Neil Conway 提交于
-
- 13 2月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME Joachim Wieland
-
- 12 2月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
Joachim Wieland
-
- 05 2月, 2006 1 次提交
-
-
由 Tom Lane 提交于
... in fact, it will be applied now in any query whatsoever. I'm still a bit concerned about the cycles that might be expended in failed proof attempts, but given that CE is turned off by default, it's the user's choice whether to expend those cycles or not. (Possibly we should change the simple bool constraint_exclusion parameter to something more fine-grained?)
-
- 23 12月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
SET.
-
- 05 11月, 2005 2 次提交
-
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
- 04 11月, 2005 1 次提交
-
-
由 Tom Lane 提交于
necessary, and be careful to refer to the right version where it is useful to do so. This partially reverts an ill-considered search and replace from a few months ago.
-
- 03 11月, 2005 1 次提交
-
-
由 Neil Conway 提交于
elsewhere.
-
- 02 11月, 2005 1 次提交
-
-
由 Neil Conway 提交于
From Simon Riggs; cleanup and editorialization by Neil Conway.
-
- 24 10月, 2005 1 次提交
-
-
由 Tom Lane 提交于
-
- 13 8月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
>>>I think a more accurate description would be "permissions not >>>inherited by children," and that isn't necessarily a bug. >> >>I agree it may not be a bug - but it's more than the permissions not >>being inherited: the parent is affected. > > > Not really, once you understand what's happening. Unless you use > FROM ONLY, selecting from the parent selects from the parent *and* > its children. The parent itself isn't affected, as queries with > FROM ONLY should demonstrate. I understand what you're saying -- > that there's an apparent effect on the parent -- but there really > isn't. Sean Burlington
-
- 12 8月, 2005 1 次提交
-
-
由 Tom Lane 提交于
whenever we generate a new OID. This prevents occasional duplicate-OID errors that can otherwise occur once the OID counter has wrapped around. Duplicate relfilenode values are also checked for when creating new physical files. Per my recent proposal.
-
- 14 7月, 2005 1 次提交
-
-
由 Neil Conway 提交于
is used as if it were the latest (and/or still valid) SQL standard. SQL:2003 is used in its place. Patch from Simon Riggs.
-