- 29 8月, 2012 7 次提交
-
-
由 Alvaro Herrera 提交于
This lets files that are mere users of ResourceOwner not automatically include the headers for stuff that is managed by the resowner mechanism.
-
由 Alvaro Herrera 提交于
-
由 Tom Lane 提交于
Per Peter Geoghegan.
-
由 Tom Lane 提交于
Since we're not installing this file anymore, it has no reason to exist, other than as historical reference; but we have an SCM for that.
-
由 Bruce Momjian 提交于
percentage column before count column. Docs updated.
-
由 Bruce Momjian 提交于
has no space before it. Report by Erik Rijkers
-
由 Bruce Momjian 提交于
Lane's correction.
-
- 28 8月, 2012 10 次提交
-
-
由 Alvaro Herrera 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
David E. Wheeler
-
由 Tom Lane 提交于
Clarify the compatibility notes about EXTRACT() and about statistics timing columns.
-
由 Tom Lane 提交于
This is so that these sections will have stable HTML tags that one can link to, rather than things like "AEN1902". Perhaps we should mount a campaign to do this everywhere, but I've found myself pointing at syntax.sgml subsections often enough to be sure it's useful here.
-
由 Bruce Momjian 提交于
pg_restore.
-
由 Alvaro Herrera 提交于
The previous signature made it very easy to pass something other than the printf-format specifier in the corresponding position, without any warning from the compiler. While at it, move some of the escaping, redirecting and quoting responsibilities from the callers into exec_prog() itself. This makes the callsites cleaner.
-
由 Alvaro Herrera 提交于
It was confusing symlinks with hard links.
-
由 Alvaro Herrera 提交于
-
- 27 8月, 2012 6 次提交
-
-
由 Bruce Momjian 提交于
has been created by adding #include <stdlib.h> to parse.c. per request from Kevin Grittner.
-
由 Heikki Linnakangas 提交于
This enables selectivity estimation of the <<, >>, &<, &> and && operators, as well as the normal inequality operators: <, <=, >=, >. "range @> element" is also supported, but the range-variant @> and <@ operators are not, because they cannot be sensibly estimated with lower and upper bound histograms alone. We would need to make some assumption about the lengths of the ranges for that. Alexander's patch included a separate histogram of lengths for that, but I left that out of the patch for simplicity. Hopefully that will be added as a followup patch. The fraction of empty ranges is also calculated and used in estimation. Alexander Korotkov, heavily modified by me.
-
由 Peter Eisentraut 提交于
It still thought that the --xlog-method option argument could be empty, as in a previous version of this feature.
-
由 Bruce Momjian 提交于
Brad Davis
-
由 Tom Lane 提交于
This patch takes care of a number of problems having to do with failure to choose valid join orders and incorrect handling of lateral references pulled up from subqueries. Notable changes: * Add a LateralJoinInfo data structure similar to SpecialJoinInfo, to represent join ordering constraints created by lateral references. (I first considered extending the SpecialJoinInfo structure, but the semantics are different enough that a separate data structure seems better.) Extend join_is_legal() and related functions to prevent trying to form unworkable joins, and to ensure that we will consider joins that satisfy lateral references even if the joins would be clauseless. * Fill in the infrastructure needed for the last few types of relation scan paths to support parameterization. We'd have wanted this eventually anyway, but it is necessary now because a relation that gets pulled up out of a UNION ALL subquery may acquire a reltargetlist containing lateral references, meaning that its paths *have* to be parameterized whether or not we have any code that can push join quals down into the scan. * Compute data about lateral references early in query_planner(), and save in RelOptInfo nodes, to avoid repetitive calculations later. * Assorted corner-case bug fixes. There's probably still some bugs left, but this is a lot closer to being real than it was before.
-
由 Bruce Momjian 提交于
for CREATE TABLE LIKE ... INCLUDING INDEXES. Per report from david.sahagian@emc.com
-
- 26 8月, 2012 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
the same as \copy.
-
由 Bruce Momjian 提交于
ISO "T" timestamptz format.
-
- 25 8月, 2012 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
The GUC check hooks for transaction_read_only and transaction_isolation tried to check RecoveryInProgress(), so as to disallow setting read/write mode or serializable isolation level (respectively) in hot standby sessions. However, GUC check hooks can be called in many situations where we're not connected to shared memory at all, resulting in a crash in RecoveryInProgress(). Among other cases, this results in EXEC_BACKEND builds crashing during child process start if default_transaction_isolation is serializable, as reported by Heikki Linnakangas. Protect those calls by silently allowing any setting when not inside a transaction; which is okay anyway since these GUCs are always reset at start of transaction. Also, add a check to GetSerializableTransactionSnapshot() to complain if we are in hot standby. We need that check despite the one in check_XactIsoLevel() because default_transaction_isolation could be serializable. We don't want to complain any sooner than this in such cases, since that would prevent running transactions at all in such a state; but a transaction can be run, if SET TRANSACTION ISOLATION is done before setting a snapshot. Per report some months ago from Robert Haas. Back-patch to 9.1, since these problems were introduced by the SSI patch. Kevin Grittner and Tom Lane, with ideas from Heikki Linnakangas
-
- 24 8月, 2012 3 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
When an invalid query parameter is reported, some memory leaks. found by Coverity
-
由 Tom Lane 提交于
If we revoke a grant option from some role X, but X still holds the option via another grant, we should not recursively revoke the privilege from role(s) Y that X had granted it to. This was supposedly fixed as one aspect of commit 4b2dafcc, but I must not have tested it, because in fact that code never worked: it forgot to shift the grant-option bits back over when masking the bits being revoked. Per bug #6728 from Daniel German. Back-patch to all active branches, since this has been wrong since 8.0.
-
- 23 8月, 2012 8 次提交
-
-
由 Heikki Linnakangas 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
Just to check that they actually work.
-
由 Tom Lane 提交于
As of 9.2, constraint exclusion should work okay with prepared statements: the planner will try custom plans with actual values of the parameters, and observe that they are a lot cheaper than the generic plan, and thus never fall back to using the generic plan. Noted by Tatsuhito Kasahara.
-
由 Tom Lane 提交于
This is open to debate of course, but it's past time we had *something* here.
-
由 Tom Lane 提交于
A very large number of small improvements ...
-
由 Tom Lane 提交于
The docs claimed that this mode only waits for the standby to receive WAL data, but actually it waits for the data to be written out to the standby's OS; which is a pretty significant difference because it removes the risk of crash of the walreceiver process.
-
由 Bruce Momjian 提交于
-