- 02 Apr, 2010 5 commits
-
-
Magnus Hagander authored
Josh Kupershmidt
-
Magnus Hagander authored
Josh Kupershmidt
-
Peter Eisentraut authored
The previous coding failed in various scenarios possibly including vpath builds and doing make install without preceding make all.
-
Simon Riggs authored
This allows us to see what mode the server is in before it starts to perform actions that can block or hang. Otherwise server messages may not appear until after messages that say FATAL the database server is starting up.
-
Michael Meskes authored
corrupted. This error, however, does is not a compilation problem but a runtime one, so we can keep compiling but still have to declare ERROR.
-
- 01 Apr, 2010 10 commits
-
-
Heikki Linnakangas authored
Windows, thanks to a feature in CRT called Parameter Validation. Backpatch to 8.2, which is the oldest version supported on Windows. In 8.2 and 8.3 also backpatch the earlier change to use DEVNULL instead of NULL_DEV #define for a /dev/null-like device. NULL_DEV was hard-coded to "/dev/null" regardless of platform, which didn't work on Windows, while DEVNULL works on all platforms. Restarting syslogger didn't work on Windows on versions 8.3 and below because of that.
-
Andrew Dunstan authored
Use a file of patterns of filenames to exclude from pgindent runs, instead if using multiple invocations of egrep. Add perl ppport.h to the current list.
-
Bruce Momjian authored
-
Michael Meskes authored
Zoltan beautified his hidden-variable-patch for ecpg. This also makes sure we get an error message instead of a warning if the variable have different types.
-
Michael Meskes authored
Applied Zoltan's patch to make ecpg spit out warnings if a local variable hides a global one with the same name.
-
Bruce Momjian authored
Takahiro Itagaki
-
Robert Haas authored
The error message now makes explicit reference to the GUC that must be changed to fix the problem, using wording suggested by Tom Lane. Along the way, rename the GUC from MaxWalSenders to max_wal_senders for consistency and grep-ability.
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
more appropriate place for exclusion constraints.
-
- 31 Mar, 2010 9 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Heikki Linnakangas authored
-
Heikki Linnakangas authored
Original patch by Fujii Masao, with heavy editing and bitrot-fixing after my other commit.
-
Heikki Linnakangas authored
"replication" are quoted in pg_hba.conf, they lose their special meaning.
-
Heikki Linnakangas authored
loop in standby mode, trying to restore from archive, pg_xlog and streaming. Move sections around to make the high availability chapter more coherent: the most prominent part is now a "Log-Shipping Standby Servers" section that describes what a standby server is (like the old "Warm Standby Servers for High Availability" section), and how to set up a warm standby server, including streaming replication, using the built-in standby mode. The pg_standby method is desribed in another section called "Alternative method for log shipping", with the added caveat that it doesn't work with streaming replication.
-
Bruce Momjian authored
default values, with example comments.
-
Michael Meskes authored
-
- 30 Mar, 2010 6 commits
-
-
Tom Lane authored
constraint exclusion on an inheritance set that is the target of an UPDATE or DELETE query. Per gripe from Marc Cousin. Back-patch to 8.4 where the feature was introduced.
-
Heikki Linnakangas authored
pg_xlog directory. This is essential for replaying WAL records that were streamed from the master, after a standby server restart. If a corrupt record is seen in a file restored from the archive or streamed from the master, log it as a WARNING and keep retrying. If the corruption is permanent, and not just a glitch in the whatever copies the files to the archive or a network error not caught by CRC checks in TCP for example, we will keep retrying and logging the WARNING indefinitely. But that's better than shutting down completely, the standby is still useful for running read-only queries. In PITR the recovery ends at such a corrupt record, which is a bit questionable, but that's the behavior we had in previous releases and we don't feel like chaning it now. It does make sense for tools like pg_standby.
-
Peter Eisentraut authored
-
Bruce Momjian authored
btree_xlog_delete_get_latestRemovedXid(). This variable was only tested in assert builds.
-
Bruce Momjian authored
-
Peter Eisentraut authored
It is no longer installed by default, but included in "make world"/"make install-world". Documentation updated accordingly. Also, fix vpathsearch function to work when calling make install-docs without previous make docs.
-
- 29 Mar, 2010 4 commits
-
-
Peter Eisentraut authored
requested by Andrew Lardinois
-
Peter Eisentraut authored
Similar information already appears in the PL/Perl and PL/Tcl chapters.
-
Peter Eisentraut authored
suggested by Steve White (bug #5272)
-
Simon Riggs authored
example to 'on or 'off' rather than 'true' or 'false', as shown in docs. Add restartpoint_command. Add section header for recovery target parameters, matching docs.
-
- 28 Mar, 2010 2 commits
-
-
Tom Lane authored
fixes things so that it works for cases where nested removals are possible. The overhead of the optimization should be significantly less, as well.
-
Simon Riggs authored
WAL record for btree delete contains a list of tids, even when backup blocks are present. We follow the tids to their heap tuples, taking care to follow LP_REDIRECT tuples. We ignore LP_DEAD tuples on the understanding that they will always have xmin/xmax earlier than any LP_NORMAL tuples referred to by killed index tuples. Iff all tuples are LP_DEAD we return InvalidTransactionId. The heap relfilenode is added to the WAL record, requiring API changes to pass down the heap Relation. XLOG_PAGE_MAGIC updated.
-
- 26 Mar, 2010 1 commit
-
-
Heikki Linnakangas authored
not delayed until the first WAL record is sent. Fujii Masao
-
- 25 Mar, 2010 3 commits
-
-
Simon Riggs authored
-
Tom Lane authored
unsatisfiable query, such as indexcol && empty_array. It should return -1 to tell GIN no scan is required; but silly typo disabled the logic for that, resulting in unnecessary "GIN indexes do not support whole-index scans" error. Per bug report from Jeff Trout. Back-patch to 8.3 where the logic was introduced.
-
Alvaro Herrera authored
by a superuser -- "ALTER USER f RESET setting" already disallows removing such a setting. Apply the same treatment to ALTER DATABASE d RESET ALL when run by a database owner that's not superuser.
-