- 08 7月, 2013 4 次提交
-
-
由 Tom Lane 提交于
The code in set_append_rel_pathlist() for building parameterized paths for append relations (inheritance and UNION ALL combinations) supposed that the cheapest regular path for a child relation would still be cheapest when reparameterized. Which might not be the case, particularly if the added join conditions are expensive to compute, as in a recent example from Jeff Janes. Fix it to compare child path costs *after* reparameterizing. We can short-circuit that if the cheapest pre-existing path is already parameterized correctly, which seems likely to be true often enough to be worth checking for. Back-patch to 9.2 where parameterized paths were introduced.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
Use "MXID" as placeholder for -m option, instead of just "XID".
-
由 Bruce Momjian 提交于
Document that tablespaces and pg_xlog can be on different file systems for pg_upgrade --link mode. Backpatch to 9.3.
-
- 07 7月, 2013 5 次提交
-
-
由 Magnus Hagander 提交于
Looks like a cut/paste error in the original addition of the file. Andres Freund
-
由 Peter Eisentraut 提交于
Explicitly ignore return value from write(), to silence warning. This warning only appeared under --disable-thread-safety.
-
由 Peter Eisentraut 提交于
Avoid output formatting differences by printing str() instead of repr() of the value.
-
由 Jeff Davis 提交于
On some platforms, posix_fallocate() is available but may still return EINVAL if the underlying filesystem does not support it. So, in case of an error, fall through to the alternate implementation that just writes zeros. Per buildfarm failure and analysis by Tom Lane.
-
由 Michael Meskes 提交于
-
- 06 7月, 2013 4 次提交
-
-
由 Tom Lane 提交于
Commit 31a89185 added some tests in plpgsql.sql that used a function rather unthinkingly named "foo()". However, rangefuncs.sql has some much older tests that create a function of that name, and since these test scripts run in parallel, there is a chance of failures if the timing is just right. Use another name to avoid that. Per buildfarm (failure seen today on "hamerkop", but probably it's happened before and not been noticed).
-
由 Peter Eisentraut 提交于
The old implementation converted PostgreSQL numeric to Python float, which was always considered a shortcoming. Now numeric is converted to the Python Decimal object. Either the external cdecimal module or the standard library decimal module are supported. From: Szymon Guz <mabewlun@gmail.com> From: Ronan Dunklau <rdunklau@gmail.com> Reviewed-by: NSteve Singer <steve@ssinger.info>
-
由 Noah Misch 提交于
All instances of the verbiage lagging the code. Back-patch to 9.3, where materialized views were introduced.
-
由 Jeff Davis 提交于
This function is more efficient than actually writing out zeroes to the new file, per microbenchmarks by Jon Nelson. Also, it may reduce the likelihood of WAL file fragmentation. Jon Nelson, with review by Andres Freund, Greg Smith and me.
-
- 05 7月, 2013 7 次提交
-
-
由 Magnus Hagander 提交于
Erikjan Rijkers
-
由 Magnus Hagander 提交于
Reported by Kevin Hale Boyes
-
由 Magnus Hagander 提交于
This value, now pg_stat_all_tables.n_mod_since_analyze, was already tracked and used by autovacuum, but not exposed to the user. Mark Kirkwood, review by Laurenz Albe
-
由 Michael Meskes 提交于
-
由 Noah Misch 提交于
Commit 263865a4 switched tuplesort.c and tuplestore.c variables representing memory usage from type "long" to type "Size". This was unnecessary; I thought doing so avoided overflow scenarios on 64-bit Windows, but guc.c already limited work_mem so as to prevent the overflow. It was also incomplete, not touching the logic that assumed a signed data type. Change the affected variables to "int64". This is perfect for 64-bit platforms, and it reduces the need to contemplate platform-specific overflow scenarios. It also puts us close to being able to support work_mem over 2 GiB on 64-bit Windows. Per report from Andres Freund.
-
由 Fujii Masao 提交于
Michael Paquier
-
由 Bruce Momjian 提交于
Comment: This code erroneously assumes '\.' on a line alone inside a quoted CSV string terminates the \copy. http://www.postgresql.org/message-id/E1TdNVQ-0001ju-GO@wrigleys.postgresql.org
-
- 04 7月, 2013 11 次提交
-
-
由 Bruce Momjian 提交于
Backpatch to 9.3. Idea from Craig Ringer
-
由 Robert Haas 提交于
In 9.3, there's no particular limit on the number of bgworkers; instead, we just count up the number that are actually registered, and use that to set MaxBackends. However, that approach causes problems for Hot Standby, which needs both MaxBackends and the size of the lock table to be the same on the standby as on the master, yet it may not be desirable to run the same bgworkers in both places. 9.3 handles that by failing to notice the problem, which will probably work fine in nearly all cases anyway, but is not theoretically sound. A further problem with simply counting the number of registered workers is that new workers can't be registered without a postmaster restart. This is inconvenient for administrators, since bouncing the postmaster causes an interruption of service. Moreover, there are a number of applications for background processes where, by necessity, the background process must be started on the fly (e.g. parallel query). While this patch doesn't actually make it possible to register new background workers after startup time, it's a necessary prerequisite. Patch by me. Review by Michael Paquier.
-
由 Robert Haas 提交于
BGWORKER_BACKEND_DATABASE_CONNECTION can only be used if BGWORKER_SHMEM_ACCESS is also used. Michael Paquier, with some tweaks by me.
-
由 Peter Eisentraut 提交于
From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
-
由 Peter Eisentraut 提交于
From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
-
由 Andrew Dunstan 提交于
Bug introduced by commit 6697aa2b and reported by Robert Haas.
-
由 Fujii Masao 提交于
Treat TOAST index just the same as normal one and get the OID of TOAST index from pg_index but not pg_class.reltoastidxid. This change allows us to handle multiple TOAST indexes, and which is required infrastructure for upcoming REINDEX CONCURRENTLY feature. Patch by Michael Paquier, reviewed by Andres Freund and me.
-
由 Bruce Momjian 提交于
Improve documentation for usagecount and relforknumber. Backpatch to 9.3. Suggestion from Satoshi Nagayasu
-
由 Robert Haas 提交于
This reverts commit 26364530. The buildfarm is sad.
-
由 Robert Haas 提交于
The collate.linux.utf8 test covers some of the same territory, but isn't portable and so probably does not get run often, or on non-Linux platforms. If this approach turns out to be sufficiently portable, we may want to look at trimming the redundant tests out of that file to avoid duplication. Robins Tharakan, reviewed by Michael Paquier and Fabien Coelho, with further changes and cleanup by me.
-
由 Tom Lane 提交于
An INSERT into such a view should work just like an INSERT into its base table, ie the insertion should go directly into that table ... not be duplicated into each child table, as was happening before, per bug #8275 from Rushabh Lathia. On the other hand, the current behavior for UPDATE/DELETE seems reasonable: the update/delete traverses the child tables, or not, depending on whether the view specifies ONLY or not. Add some regression tests covering this area. Dean Rasheed
-
- 03 7月, 2013 9 次提交
-
-
由 Alvaro Herrera 提交于
In patch 82233ce7, AbortStartTime wasn't being reset appropriately after the restart sequence, causing subsequent iterations through ServerLoop to malfunction.
-
由 Robert Haas 提交于
Robins Tharakan, reviewed by Szymon Guz
-
由 Robert Haas 提交于
Robins Tharakan, reviewed by Szymon Guz
-
由 Noah Misch 提交于
Specifically, permit attaching them to the error in RAISE and retrieving them from a caught error in GET STACKED DIAGNOSTICS. RAISE enforces nothing about the content of the fields; for its purposes, they are just additional string fields. Consequently, clarify in the protocol and libpq documentation that the usual relationships between error fields, like a schema name appearing wherever a table name appears, are not universal. This freedom has other applications; consider a FDW propagating an error from an RDBMS having no schema support. Back-patch to 9.3, where core support for the error fields was introduced. This prevents the confusion of having a release where libpq exposes the fields and PL/pgSQL does not. Pavel Stehule, lexical revisions by Noah Misch.
-
由 Peter Eisentraut 提交于
The web site is dead, and the Wayback Machine shows that it didn't have much useful content before.
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
This mirrors the equivalent error cases in pg_dump.
-
由 Robert Haas 提交于
To that end, support tags rather than lengths for external datums. As an example of how this can be used, add support or "indirect" tuples which point to some externally allocated memory containing a toast tuple. Similar infrastructure could be used for other purposes, including, perhaps, support for alternative compression algorithms. Andres Freund, reviewed by Hitoshi Harada and myself
-