- 28 7月, 2010 7 次提交
-
-
由 Simon Riggs 提交于
Avoid hard-coding lockmode used for many altering DDL commands, allowing easier future changes of lock levels. Implementation of initial analysis on DDL sub-commands, so that many lock levels are now at ShareUpdateExclusiveLock or ShareRowExclusiveLock, allowing certain DDL not to block reads/writes. First of number of planned changes in this area; additional docs required when full project complete.
-
由 Tom Lane 提交于
a pass-by-reference datatype with a nontrivial projection step. We were using the same memory context for the projection operation as for the temporary context used by the hashtable routines in execGrouping.c. However, the hashtable routines feel free to reset their temp context at any time, which'd lead to destroying input data that was still needed. Report and diagnosis by Tao Ma. Back-patch to 8.1, where the problem was introduced by the changes that allowed us to work with "virtual" tuples instead of materializing intermediate tuple values everywhere. The earlier code looks quite similar, but it doesn't suffer the problem because the data gets copied into another context as a result of having to materialize ExecProject's output tuple.
-
由 Peter Eisentraut 提交于
These two settings ought to be independent of each other.
-
由 Robert Haas 提交于
Review by Dave Page.
-
由 Robert Haas 提交于
Backpatch to 8.4. Marc Cousin. Review by Kevin Grittner.
-
由 Peter Eisentraut 提交于
-
由 Robert Haas 提交于
We used to be consistent about this, but my recent patch to add a restart_after_crash GUC failed to follow the existing convention. Report and patch from Fujii Masao.
-
- 27 7月, 2010 3 次提交
-
-
由 Alvaro Herrera 提交于
Author: Alex Hunsaker
-
由 Peter Eisentraut 提交于
backpatched to 8.1
-
由 Peter Eisentraut 提交于
from John Gage
-
- 26 7月, 2010 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Robert Haas 提交于
Reviewed by Bernd Helmle.
-
- 25 7月, 2010 4 次提交
-
-
由 Peter Eisentraut 提交于
from John Gage
-
由 Bruce Momjian 提交于
migrations. Backpatch to 9.0.
-
由 Bruce Momjian 提交于
where the oid is not preserved by pg_upgrade (everything but pg_type). Update documentation. Per bug report from depstein@alliedtesting.com.
-
由 Peter Eisentraut 提交于
-
- 24 7月, 2010 3 次提交
-
-
由 Peter Eisentraut 提交于
by Thom Brown
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
- Prohibit altering column type - Prohibit changing inheritance - Move checks from Exec to Prep phases in ALTER TABLE code backpatched to 9.0
-
- 23 7月, 2010 2 次提交
-
-
由 Robert Haas 提交于
We now use the phrase 'via local socket in' rather than 'on host' in both \c and \conninfo output, when applicable. Fujii Masao, with some kibitzing by me.
-
由 Robert Haas 提交于
Backpatch to 8.0. Andres Freund, with cleanup and adjustment for older branches by me.
-
- 22 7月, 2010 4 次提交
-
-
由 Robert Haas 提交于
Fujii Masao
-
由 Robert Haas 提交于
-
由 Robert Haas 提交于
I've added a quote_all_identifiers GUC which affects the behavior of the backend, and a --quote-all-identifiers argument to pg_dump and pg_dumpall which sets the GUC and also affects the quoting done internally by those applications. Design by Tom Lane; review by Alex Hunsaker; in response to bug #5488 filed by Hartmut Goebel.
-
由 Robert Haas 提交于
Remove bespoke code in DoCopy and RI_Initial_Check, which now instead fabricate call ExecCheckRTPerms with a manufactured RangeTblEntry. This is intended to make it feasible for an enhanced security provider to actually make use of ExecutorCheckPerms_hook, but also has the advantage that RI_Initial_Check can allow use of the fast-path when column-level but not table-level permissions are present. KaiGai Kohei. Reviewed (in an earlier version) by Stephen Frost, and by me. Some further changes to the comments by me.
-
- 21 7月, 2010 2 次提交
-
-
由 Bruce Momjian 提交于
Does modification just of CVS tag text cause an empty CVS diff for the commit?
-
由 Bruce Momjian 提交于
directory/symlink before creation. Report from Tom Lane. Backpatch to 9.0.
-
- 20 7月, 2010 7 次提交
-
-
由 Robert Haas 提交于
Per discussion with David Christensen, there can be multiple instances of PG accessible via local sockets, and you need the port to see which one you're actually connected to. David's original patch worked this way, but I inadvertently ripped it out during commit.
-
由 Robert Haas 提交于
David Christensen. Reviewed by Steve Singer. Some further changes by me.
-
由 Robert Haas 提交于
Per buildfarm, again.
-
由 Robert Haas 提交于
Per buildfarm.
-
由 Robert Haas 提交于
Normally, we automatically restart after a backend crash, but in some cases when PostgreSQL is invoked by clusterware it may be desirable to suppress this behavior, so we provide an option which does this. Since no existing GUC group quite fits, create a new group called "error handling options" for this and the previously undocumented GUC exit_on_error, which is now documented. Review by Fujii Masao.
-
由 Robert Haas 提交于
This change should be publicized to driver maintainers at once and release-noted as an incompatibility with previous releases.
-
由 Peter Eisentraut 提交于
per report from Dave Page
-
- 19 7月, 2010 4 次提交
-
-
由 Tom Lane 提交于
path when CSV logging is configured but not yet operational. It's sufficient to send the message to stderr, as we were already doing, and the "Not safe" gripe has already confused at least two core members ... Backpatch to 9.0, but not further --- doesn't seem appropriate to change this behavior in stable branches.
-
由 Tom Lane 提交于
any implicit casting previously applied to the targetlist item. This is reasonable because the implicit cast, by definition, wasn't written by the user; so we are preserving the expected behavior that ORDER BY items match textually equivalent tlist items. The case never arose before because there couldn't be any implicit casting of a top-level SELECT item before we process ORDER BY etc. But now it can arise in the context of aggregates containing ORDER BY clauses, since the "targetlist" is the already-casted list of arguments for the aggregate. The net effect is that the datatype used for ORDER BY/DISTINCT purposes is the aggregate's declared input type, not that of the original input column; which is a bit debatable but not horrendous, and to do otherwise would require major rework that doesn't seem justified. Per bug #5564 from Daniel Grace. Back-patch to 9.0 where aggregate ORDER BY was implemented.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
- 18 7月, 2010 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
This adds a libpq connection parameter requirepeer that specifies the user name that the server process is expected to run under. reviewed by KaiGai Kohei
-