- 23 8月, 2012 3 次提交
-
-
由 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 提交于
-
由 Bruce Momjian 提交于
configuration file.
-
- 22 8月, 2012 5 次提交
-
-
由 Peter Eisentraut 提交于
There was a hack put into install-sh to call strip with the correct options on Mac OS X. But that never worked, because configure disabled stripping on that platform altogether. So remove that dead code, and while we're at it, update install-sh to the latest upstream source (from Automake). Instead, set up the right strip options in programs.m4, so this now actually works the way it was originally intended.
-
由 Peter Eisentraut 提交于
This avoids a warning from clang 3.2 about an uninitialized variable 'dtype' in date_in().
-
由 Tom Lane 提交于
I was unable to entirely resist the temptation to copy-edit related entries, but will save most of that for a separate pass.
-
由 Tom Lane 提交于
This improves on commit 51fed14d by eliminating the assumption that we can form <some pointer value> + <some offset> without overflow. The entire point of those tests is that we don't trust the offset value, so coding them in a way that could wrap around if the buffer happens to be near the top of memory doesn't seem sound. Instead, track the remaining space as a size_t variable and compare offsets against that. Also, improve comment about why we need the extra early check on xl_tot_len.
-
由 Tom Lane 提交于
If a view has circular dependencies, pg_dump splits it into a CREATE TABLE and a CREATE RULE command to break the dependency loop. However, if the view has reloptions, those options cannot be applied in the CREATE TABLE command, because views and tables have different allowed reloptions so CREATE TABLE would reject them. Instead apply the reloptions after the CREATE RULE, using ALTER VIEW SET.
-
- 21 8月, 2012 8 次提交
-
-
由 Robert Haas 提交于
Move discussion of why our algorithm for taking snapshots in recovery to a more appropriate location in the function, and delete incorrect mention of taking a lock.
-
由 Robert Haas 提交于
Craig Ringer, slightly edited by me.
-
由 Peter Eisentraut 提交于
When elevel >= ERROR, we add an abort() call to the ereport() macro to give the compiler a hint that the ereport() expansion will not return, but the abort() isn't actually reached because the longjmp happens in errfinish(). Because the effect of ereport() varies with the elevel, we cannot use standard compiler attributes such as noreturn for this.
-
由 Peter Eisentraut 提交于
-
由 Robert Haas 提交于
Jeff Janes
-
由 Robert Haas 提交于
Jeff Janes
-
由 Tom Lane 提交于
Extraction of trigrams did not process LIKE escape sequences properly, leading to possible misidentification of trigrams near escapes, resulting in incorrect index search results. Fujii Masao
-
由 Heikki Linnakangas 提交于
If a WAL record header was split across pages, but xl_tot_len was 0, we would get confused and conclude that we had already read the whole record, and proceed to CRC check it. That can lead to a crash in RecordIsValid(), which isn't careful to not read beyond end-of-record, as defined by xl_tot_len. Add an explicit sanity check for xl_tot_len <= SizeOfXlogRecord. Also, make RecordIsValid() more robust by checking in each step that it doesn't try to access memory beyond end of record, even if a length field in the record's or a backup block's header is bogus. Per report and analysis by Tom Lane.
-
- 20 8月, 2012 3 次提交
- 19 8月, 2012 2 次提交
-
-
由 Tom Lane 提交于
It said "XXX: The following could be improved if we had LATERAL" ... so let's do that. No catversion bump since either version of the view works fine.
-
由 Tom Lane 提交于
Formerly, subquery pullup had no need to examine other entries in the range table, since they could not contain any references to the subquery being pulled up. That's no longer true with LATERAL, so now we need to be able to visit rangetable subexpressions to replace Vars referencing the pulled-up subquery. Also, this means that extract_lateral_references must be unsurprised at encountering lateral PlaceHolderVars, since such might be created when pulling up a subquery that's underneath an outer join with respect to the lateral reference.
-
- 18 8月, 2012 1 次提交
-
-
由 Tom Lane 提交于
Fix grammar, put back some removed information, rearrange for clarity.
-
- 17 8月, 2012 8 次提交
-
-
由 Tom Lane 提交于
We had put a test for libxml2's xmlStructuredErrorContext variable in configure, but of course that doesn't work on Windows builds. The next best alternative seems to be to test the LIBXML_VERSION symbol provided by xmlversion.h. Per report from Talha Bin Rizwan, though this fixes it in a different way than his proposed patch.
-
由 Bruce Momjian 提交于
from Dmitriy Igrishin
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
In the initial cut at the "parameterized paths" feature, I'd simplified create_index_paths() to the point where it would only generate a single parameterized bitmap path per relation. Experimentation with an example supplied by Josh Berkus convinces me that that's not good enough: we really need to consider a bitmap path for each possible outer relation. Otherwise we have regressions relative to pre-9.2 versions, in which the planner picks a plain indexscan where it should have used a bitmap scan in queries involving three or more tables. Indeed, after fixing this, several queries in the regression tests show improved plans as a result of using bitmap not plain indexscans.
-
由 Tom Lane 提交于
-
- 16 8月, 2012 10 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
the partition.
-
由 Bruce Momjian 提交于
"unimportant". Per request from Heikki
-
由 Bruce Momjian 提交于
keywords and concepts, based on suggestions by Florian Pflug.
-
由 Bruce Momjian 提交于
-
由 Heikki Linnakangas 提交于
The implementation is a quad-tree, largely copied from the quad-tree implementation for points. The lower and upper bound of ranges are the 2d coordinates, with some extra code to handle empty ranges. I left out the support for adjacent operator, -|-, from the original patch. Not because there was necessarily anything wrong with it, but it was more complicated than the other operators, and I only have limited time for reviewing. That will follow as a separate patch. Alexander Korotkov, reviewed by Jeff Davis and me.
-
由 Heikki Linnakangas 提交于
We use a hash table to track the parents of inner pages, but when inserting to a leaf page, the caller of gistbufferinginserttuples() must pass a correct block number of the leaf's parent page. Before gistProcessItup() descends to a child page, it checks if the downlink needs to be adjusted to accommodate the new tuple, and updates the downlink if necessary. However, updating the downlink might require splitting the page, which might move the downlink to a page to the right. gistProcessItup() doesn't realize that, so when it descends to the leaf page, it might pass an out-of-date parent block number as a result. Fix that by returning the block a tuple was inserted to from gistbufferinginserttuples(). This fixes the bug reported by Zdeněk Jílovec.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
than the actual data storage directory. Per suggestion from Thom Brown
-
由 Bruce Momjian 提交于
startup. Per report from Thom Brown
-