- 02 7月, 2010 1 次提交
-
-
由 Robert Haas 提交于
This makes ALTER DATABASE .. SET TABLESPACE and CREATE DATABASE more sensitive to interrupts. Backpatch to 8.4, where ALTER DATABASE .. SET TABLESPACE was introduced. We could go back further, but in the absence of complaints about the CREATE DATABASE case it doesn't seem worth it. Guillaume Lelarge, with a small correction by me.
-
- 01 7月, 2010 5 次提交
-
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Robert Haas 提交于
Backpatch to 8.0, where tablespaces were introduced. Guillaume Lelarge
-
由 Bruce Momjian 提交于
assumed to require continuous archiving. Per report from Fujii Masao
-
由 Heikki Linnakangas 提交于
but we have nevertheless exposed them to users via pg_get_expr(). It would be too much maintenance effort to rigorously check the input, so put a hack in place instead to restrict pg_get_expr() so that the argument must come from one of the system catalog columns known to contain valid expressions. Per report from Rushabh Lathia. Backpatch to 7.4 which is the oldest supported version at the moment.
-
- 30 6月, 2010 6 次提交
-
-
由 Andrew Dunstan 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
between words).
-
由 Bruce Momjian 提交于
lowercase the library names, unless double-quoted.
-
由 Tom Lane 提交于
datatypes of composite results, per gripe from Marcel Asio. Some desultory copy-editing of plpgsql-related sections of the release notes.
-
由 Bruce Momjian 提交于
committed transactions in a postmaster crash.
-
- 29 6月, 2010 7 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
pg_pltemplate This should have a catversion bump, but it's still being debated whether it's worth it during beta.
-
由 Peter Eisentraut 提交于
per complaint from Craig Ringer
-
由 Bruce Momjian 提交于
Report from Thom Brown
-
由 Bruce Momjian 提交于
Document that synchronous_commit can lose transactions in a db crash, not just a OS crash.
-
由 Robert Haas 提交于
In non-interactive sessions, WARNING sorts below LOG.
-
由 Peter Eisentraut 提交于
-
- 28 6月, 2010 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
as well as fseeko, and to not assume that fseeko(fp, 0, SEEK_CUR) proves anything. Also improve some related comments. Per my observation that the SEEK_CUR test didn't actually work on some platforms, and subsequent discussion with Robert Haas. Back-patch to 8.4. In earlier releases it's not that important whether we get the hasSeek test right, but with parallel restore it matters.
-
由 Tom Lane 提交于
contain data offsets (which it won't, if pg_dump thought its output wasn't seekable). To do that, remove an unnecessarily aggressive error check, and instead fail if we get to the end of the archive without finding the desired data item. Also improve the error message to be more specific about the cause of the problem. Per discussion of recent report from Igor Neyman. Back-patch to 8.4 where parallel restore was introduced.
-
- 26 6月, 2010 3 次提交
-
-
由 Robert Haas 提交于
The revised documentation makes it more clear that these are client-side parameters, rather than server side parameters. It also puts the main point of each parameter first, and consolidates the conditions under which it might be ignored in a single list at the end.
-
由 Robert Haas 提交于
Chris Browne, based on a report from John Pierce.
-
由 Tom Lane 提交于
of YYSTYPE, and hence returning the wrong answer for cases where a plpgsql "unreserved keyword" really does conflict with a variable name. Obviously I didn't test this enough :-(. Per bug #5524 from Peter Gagarinov.
-
- 25 6月, 2010 4 次提交
-
-
由 Simon Riggs 提交于
stat(2) field st_size returns bytes not kilobytes. Bug found during recent performance tuning for PostgreSQL user.
-
由 Robert Haas 提交于
Thanks to Joshua Tolley for the review.
-
由 Robert Haas 提交于
Josh Berkus
-
由 Robert Haas 提交于
-
- 24 6月, 2010 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Robert Haas 提交于
This adds four additional connection parameters to libpq: keepalives, keepalives_idle, keepalives_count, and keepalives_interval. keepalives default to on, per discussion, but can be turned off by specifying keepalives=0. The remaining parameters, where supported, can be used to adjust how often keepalives are sent and how many can be lost before the connection is broken. The immediate motivation for this patch is to make sure that walreceiver will eventually notice if the master reboots without closing the connection cleanly, but it should be helpful in other cases as well. Tollef Fog Heen, Fujii Masao, and me.
-
由 Bruce Momjian 提交于
-
- 23 6月, 2010 2 次提交
-
-
由 Bruce Momjian 提交于
output to the same file, because it is impossible. Also set user name for pg_dumpall in pg_upgrade.
-
由 Bruce Momjian 提交于
win32 and non-win32 platforms.
-
- 22 6月, 2010 3 次提交
-
-
由 Robert Haas 提交于
This is an oversight in my previous patch to deprecate => as an operator name. Per buildfarm.
-
由 Robert Haas 提交于
In HEAD, emit a warning when an operator named => is defined. In both HEAD and the backbranches (except in 8.2, where contrib modules do not have documentation), document that hstore's text => text operator may be removed in a future release, and encourage the use of the hstore(text, text) function instead. This function only exists in HEAD (previously, it was called tconvert), so backpatch it back to 8.2, when hstore was added. Per discussion.
-
由 Robert Haas 提交于
-
- 21 6月, 2010 2 次提交
-
-
由 Heikki Linnakangas 提交于
might close the cursor, rendering the Portal pointer to it invalid. Closing the cursor in the middle of the loop is not a very sensible thing to do, but we must handle it gracefully and throw an error instead of crashing.
-
由 Tom Lane 提交于
If such a Var appeared within a nested sub-select, we failed to translate it correctly during pullup of the view, because the recursive call to replace_rte_variables_mutator was looking for the wrong sublevels_up value. Bug was introduced during the addition of the PlaceHolderVar mechanism. Per bug #5514 from Marcos Castedo.
-
- 18 6月, 2010 1 次提交
-
-
由 Robert Haas 提交于
This is not yet in any released version, so we still have the option to change the name. We may want to reserve the token => in a future release.
-