- 22 7月, 2010 1 次提交
-
-
由 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 3 次提交
-
-
由 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
-
由 Bruce Momjian 提交于
so we don't need to re-translate for 9.0.
-
- 17 7月, 2010 1 次提交
-
-
由 Tom Lane 提交于
log files created by the syslogger process. In passing, make unix_file_permissions display its value in octal, same as log_file_mode now does. Martin Pihlak
-
- 16 7月, 2010 5 次提交
-
-
由 Heikki Linnakangas 提交于
-
由 Heikki Linnakangas 提交于
wal_keep_segments does not take effect during recovery. Fujii Masao
-
由 Tom Lane 提交于
casting between money and numeric. Andy Balholm, reviewed by Kevin Grittner
-
由 Tom Lane 提交于
from defining non-self-conflicting constraints. Jeff Davis Note: I (tgl) objected to removing this check in 9.0 on the grounds that it was an important sanity check in new, poorly tested code. However, it should be all right to remove it for 9.1, since we'll get field testing from the 9.0 branch.
-
由 Tom Lane 提交于
The code was probably meant to be this way all along, since the subroutine CreateOpFamily previously had only one caller. But it wasn't. KaiGai Kohei
-
- 15 7月, 2010 3 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
to dump a PUBLIC user mapping correctly, as per bug #5560 from Shigeru Hanada. Use the pg_user_mappings view rather than trying to access pg_user_mapping directly, so that the code doesn't fail when run by a non-superuser. And clean up some minor carelessness such as unsafe usage of fmtId(). Back-patch to 8.4 where this code was added.
-
由 Tom Lane 提交于
parameter against server cert's CN field) to succeed in the case where both host and hostaddr are specified. As with the existing precedents for Kerberos, GSSAPI, SSPI, it is the calling application's responsibility that host and hostaddr match up --- we just use the host name as given. Per bug #5559 from Christopher Head. In passing, make the error handling and messages for the no-host-name-given failure more consistent among these four cases, and correct a lie in the documentation: we don't attempt to reverse-lookup host from hostaddr if host is missing. Back-patch to 8.4 where SSL cert verification was introduced.
-
- 14 7月, 2010 5 次提交
-
-
由 Tom Lane 提交于
rather than just $N. This brings the display of nestloop-inner-indexscan plans back to where it's been, and incidentally improves the display of SubPlan parameters as well. In passing, simplify the EXPLAIN code by having it deal primarily in the PlanState tree rather than separately searching Plan and PlanState trees. This is noticeably cleaner for subplans, and about a wash elsewhere. One small difference from previous behavior is that EXPLAIN will no longer qualify local variable references in inner-indexscan plan nodes, since it no longer sees such nodes as possibly referencing multiple tables. Vars referenced through PARAM_EXEC Params are still forcibly qualified, though, so I don't think the display is any more confusing than before. Adjust a couple of examples in the documentation to match this behavior.
-
由 Bruce Momjian 提交于
because of file access limitations on that platform.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
the end.
-
- 13 7月, 2010 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Heikki Linnakangas 提交于
loop from being dropped, I missed subtransaction cleanup. Pinned portals must be dropped at subtransaction cleanup just as they are at main transaction cleanup. Per bug #5556 by Robert Walker. Backpatch to 8.0, 7.4 didn't have subtransactions.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Erik Rijkers
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
relation using the general PARAM_EXEC executor parameter mechanism, rather than the ad-hoc kluge of passing the outer tuple down through ExecReScan. The previous method was hard to understand and could never be extended to handle parameters coming from multiple join levels. This patch doesn't change the set of possible plans nor have any significant performance effect, but it's necessary infrastructure for future generalization of the concept of an inner indexscan plan. ExecReScan's second parameter is now unused, so it's removed.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 11 7月, 2010 1 次提交
-
-
由 Tom Lane 提交于
formatting conventions.
-