- 20 3月, 2010 2 次提交
-
-
由 Simon Riggs 提交于
correctly sized and expand comment to explain otherwise undocumented use of replication connection parameter.
-
由 Simon Riggs 提交于
-
- 19 3月, 2010 6 次提交
-
-
由 Simon Riggs 提交于
present since 8.0 was never fully meaningful, since two recovery targets cannot be specified. Refactor recovery target type to make this change and associated code easier to understand. No change in function. Bug report arising from internal support question.
-
由 Simon Riggs 提交于
field into WAL record and reset it from there, rather than using FrozenTransactionId which can lead to some corner case bugs. Problem report and suggested route to a fix from Heikki, details by me.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
with a few strategically placed pg_verifymbstr calls.
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
- 18 3月, 2010 11 次提交
-
-
由 Tom Lane 提交于
Also make a couple other minor editorial improvements.
-
由 Peter Eisentraut 提交于
In PLy_spi_execute_plan, use the data-type specific Python-to-PostgreSQL conversion function instead of passing everything through InputFunctionCall as a string. The equivalent fix was already done months ago for function parameters and return values, but this other gateway between Python and PostgreSQL was apparently forgotten. As a result, data types that need special treatment, such as bytea, would misbehave when used with plpy.execute.
-
由 Heikki Linnakangas 提交于
in recovery_end_command, it always came out as 0 because InRedo was cleared before recovery_end_command was executed. Also, always take ControlFileLock when reading checkpoint location for %r. The recovery_end_command bug and the missing locking was present in 8.4 as well, that part of this patch will be backported separately.
-
由 Simon Riggs 提交于
-
由 Peter Eisentraut 提交于
This variable is apparently only for Python internally. In newer releases of Python this variable pulls in more and more libraries that users are less likely to have, leading to potential build failures.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Magnus Hagander 提交于
Fujii Masao
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
to transformAggregateCall, instead of abusing fields in Aggref to carry them temporarily. No change in functionality but hopefully the code is a bit clearer now. Per gripe from Gokulakannan Somasundaram.
-
- 17 3月, 2010 3 次提交
-
-
由 Tom Lane 提交于
Also fix and uncomment an old example of creating a GIST index, and make a couple of other minor editorial adjustments.
-
由 Simon Riggs 提交于
-
由 Simon Riggs 提交于
-
- 16 3月, 2010 3 次提交
-
-
由 Heikki Linnakangas 提交于
the master is still in recovery. We don't support cascading slaves yet. Patch by Fujii Masao, with slightly changed wording.
-
由 Simon Riggs 提交于
-
由 Simon Riggs 提交于
correct, as described in comments at start of xlog.c
-
- 14 3月, 2010 4 次提交
-
-
由 Tom Lane 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 13 3月, 2010 10 次提交
-
-
由 Bruce Momjian 提交于
Jaime Casanova
-
由 Bruce Momjian 提交于
Add ERRCODE_INVALID_PASSWORD sqlstate error code.
-
由 Peter Eisentraut 提交于
In particular, the assertion that shmall is sufficiently sized by default is slowly becoming untrue.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
by Dan O'Hara. Patch by Teodor Sigaev
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
unable to read a stats file for reasons other than ENOENT, and having to reset last_statrequest because it's later than current time in the collector. Not clear if this will shed any light on the "pgstat wait timeout" business, but it seems like a good idea in general. In passing, do some message-style-police work on recently-added pgstat_reset_shared_counters code.
-
由 Tom Lane 提交于
properly; it's been making that comment uglier with each run.
-
由 Bruce Momjian 提交于
-
- 12 3月, 2010 1 次提交
-
-
由 Tom Lane 提交于
This resulted in useless extra work during every call of parseRelOptions, but no bad effects other than that. Noted by Alvaro.
-