- 07 3月, 2011 13 次提交
-
-
由 Heikki Linnakangas 提交于
Kevin Grittner
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
assertions.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
Seen with an older gcc version. I'm not sure these represent any real risk factor, but still a bit scary. Anyway we have lots of other volatile-marked variables in this code, so a couple more won't hurt.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
Per testing with a compiler that doesn't like that.
-
由 Simon Riggs 提交于
-
由 Simon Riggs 提交于
-
由 Simon Riggs 提交于
-
由 Tom Lane 提交于
Mixing them together alphabetically won't be nice. Per my gripe of 2011-02-12.
-
由 Simon Riggs 提交于
If a standby is broadcasting reply messages and we have named one or more standbys in synchronous_standby_names then allow users who set synchronous_replication to wait for commit, which then provides strict data integrity guarantees. Design avoids sending and receiving transaction state information so minimises bookkeeping overheads. We synchronize with the highest priority standby that is connected and ready to synchronize. Other standbys can be defined to takeover in case of standby failure. This version has very strict behaviour; more relaxed options may be added at a later date. Simon Riggs and Fujii Masao, with reviews by Yeb Havinga, Jaime Casanova, Heikki Linnakangas and Robert Haas, plus the assistance of many other design reviewers.
-
由 Tom Lane 提交于
Since this field is after a variable-length field, it can't simply be accessed via the C struct for pg_index. Fortunately, the relcache already did the dirty work of pulling the information out to where it can be accessed easily, so this is a one-line fix. Andres Freund
-
- 06 3月, 2011 11 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
toast file names to match the new relfilenode.
-
由 Bruce Momjian 提交于
failures.
-
由 Bruce Momjian 提交于
error.
-
由 Bruce Momjian 提交于
-
由 Andrew Dunstan 提交于
-
由 Tom Lane 提交于
It's more likely that pg_pltemplate will go away in the future than that we'll add additional specialized infrastructure for it.
-
由 Tom Lane 提交于
The original scheme for this was to symlink plpython.$DLSUFFIX to plpython2.$DLSUFFIX, but that doesn't work on Windows, and only accidentally failed to fail because of the way that CREATE LANGUAGE created or didn't create new C functions. My changes of yesterday exposed the weakness of that approach. To fix, get rid of the symlink and make pg_pltemplate show what's really going on.
-
由 Tom Lane 提交于
In createlang this is a one-line change. In droplang there's a whole lot of cruft that can be discarded since the extension mechanism now manages removal of the language's support functions. Also, add deprecation notices to these two programs' reference pages, since per discussion we may toss them overboard altogether in a release or two.
-
由 Robert Haas 提交于
Noted by Andy Colson
-
- 05 3月, 2011 11 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Robert Haas 提交于
-
由 Robert Haas 提交于
-
由 Robert Haas 提交于
In preparation for 9.1alpha4 release notes, where only the 9.1alpha4 features will be emphasized.
-
由 Tom Lane 提交于
Recommend use of CREATE EXTENSION rather than plain CREATE LANGUAGE where relevant. Encourage PL authors to provide extension wrappers for their PLs.
-
由 Tom Lane 提交于
This mostly just involves creating control, install, and update-from-unpackaged scripts for them. However, I had to adjust plperl and plpython to not share the same support functions between variants, because we can't put the same function into multiple extensions. catversion bump forced due to new contents of pg_pltemplate, and because initdb now installs plpgsql as an extension not a bare language. Add support for regression testing these as extensions not bare languages. Fix a couple of other issues that popped up while testing this: my initial hack at pg_dump binary-upgrade support didn't work right, and we don't want an extra schema permissions test after all. Documentation changes still to come, but I'm committing now to see whether the MSVC build scripts need work (likely they do).
-
由 Robert Haas 提交于
This avoids duplicate (and not-quite-matching) code, and makes the logic for SECURITY LABEL match COMMENT and ALTER EXTENSION ADD/DROP.
-
由 Peter Eisentraut 提交于
It is possible that an expression ends up with a collatable type but without a collation. CREATE TABLE AS could then create a table based on that. But such a column cannot be dumped with valid SQL syntax, so we disallow creating such a column. per test report from Noah Misch
-
由 Tom Lane 提交于
Remove the unconditional superuser permissions check in CREATE EXTENSION, and instead define a "superuser" extension property, which when false (not the default) skips the superuser permissions check. In this case the calling user only needs enough permissions to execute the commands in the extension's installation script. The superuser property is also enforced in the same way for ALTER EXTENSION UPDATE cases. In other ALTER EXTENSION cases and DROP EXTENSION, test ownership of the extension rather than superuserness. ALTER EXTENSION ADD/DROP needs to insist on ownership of the target object as well; to do that without duplicating code, refactor comment.c's big switch for permissions checks into a separate function in objectaddress.c. I also removed the superuserness checks in pg_available_extensions and related functions; there's no strong reason why everybody shouldn't be able to see that info. Also invent an IF NOT EXISTS variant of CREATE EXTENSION, and use that in pg_dump, so that dumps won't fail for installed-by-default extensions. We don't have any of those yet, but we will soon. This is all per discussion of wrapping the standard procedural languages into extensions. I'll make those changes in a separate commit; this is just putting the core infrastructure in place.
-
由 Peter Eisentraut 提交于
This is the same check that would happen later when the collation is used, but it's friendlier to check the collation already when it is created.
-
由 Tom Lane 提交于
Instead, just act as though the certificate file(s) are not present. There is only one case where this need be a hard failure condition: when sslmode is verify-ca or verify-full, not having a root cert file is an error. Change the logic so that we complain only in that case, and otherwise fall through cleanly. This is how it used to behave pre-9.0, but my patch 4ed4b6c5 of 2010-05-26 broke the case. Per report from Christian Kastner.
-
- 04 3月, 2011 5 次提交
-
-
由 Heikki Linnakangas 提交于
CheckForSerializableConflictOut(), because it can set hint bits. YAMAMOTO Takashi
-
由 Andrew Dunstan 提交于
Mostly text supplied by Jan Urbański.
-
由 Tom Lane 提交于
Instead of manually maintaining the "implementation of XXX operator" comments in pg_proc.h, delete all those entries and let initdb create them via a join. To let initdb figure out which name to use when there is a conflict, change the comments for deprecated operators to say they are deprecated --- which seems like a good thing to do anyway.
-
由 Tom Lane 提交于
Although there remains some debate about how CREATE TYPE should represent the collation property, this doesn't really affect what we need to do in citext's script, so go ahead and fix that.
-
由 Tom Lane 提交于
This works around the problem noted by Yamamoto Takashi in bug #5906, that there were code paths whereby we could reach AtCleanup_Portals with a portal's cleanup hook still unexecuted. The changes I made a few days ago were intended to prevent that from happening, and I think that on balance it's still a good thing to avoid, so I don't want to remove the Assert in AtCleanup_Portals. Hence do this instead.
-