aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Change replication connection log format to allow for a databaseSimon Riggs2010-03-24
| | | | | called replication. Add host and port details, following format of messages in BackendInitialize().
* Reduce CPU utilisation of WALSender process. Process was using 10% CPUSimon Riggs2010-03-24
| | | | | | doing nothing, caused by naptime specified in milliseconds yet units of pg_usleep() parameter is microseconds. Correctly specifying units reduces call frequency by 1000. Reduction in CPU consumption verified.
* Fix thinko in log message for "sameuser" ident map mismatch: the providedTom Lane2010-03-24
| | | | | | | and authenticated usernames were swapped. Reported by Bryan Henderson in bug #5386. Also clean up poorly-maintained header comment for this function.
* Now that we know last_statrequest > last_statwrite can be observed in theTom Lane2010-03-24
| | | | buildfarm, expend a little more effort on the log message for it.
* Mark "installcheck-parallel", "world", "install-world" and ↵Andrew Dunstan2010-03-24
| | | | "installcheck-world" make targets as PHONY. Fujii Masao.
* Update description of walrcv_receive() function to match reality.Heikki Linnakangas2010-03-24
|
* Document in postgresql.conf that the max_standby_delay default is 30Bruce Momjian2010-03-24
| | | | 'seconds'.
* Remove useless double assignmentPeter Eisentraut2010-03-23
| | | | GCC 4.5 complained about it.
* Fix regression test breakage from recent change in default name of ↵Tom Lane2010-03-22
| | | | exclusion-constraint index.
* Shorten suffix of automatically created indexes to "_excl" when usingSimon Riggs2010-03-22
| | | | exclusion constraints, in line with string length of other pre-9.0 suffixes.
* Fix an oversight in join-removal optimization: we have to check not only forTom Lane2010-03-22
| | | | | plain Vars that are generated in the inner rel and used above the join, but also for PlaceHolderVars. Per report from Oleg K.
* Fixed ECPG regression test to make sure it uses absolute paths for includeMichael Meskes2010-03-22
| | | | files instead of relative ones which break vpath builds.
* Adding special command line option that is now needed for the one ecpg ↵Michael Meskes2010-03-21
| | | | regression test that was changed.
* ECPG's parser now accepts and handles variables as arguments for the FREE ↵Michael Meskes2010-03-21
| | | | | | | | command. Informix allows variables as argument to the embedded SQL command FREE. Given that we only allow freeing cursors via FREE for compatibility reasons only we should do the same.
* Adjusted regression test results to the change I made in debug output for ↵Michael Meskes2010-03-21
| | | | ecpglib.
* Correctly name functions in debug output in ecpglib. When the functions wereMichael Meskes2010-03-21
| | | | refactored the debug output wasn't adjusted.
* ECPG only copied #include statements instead of processing them according toMichael Meskes2010-03-21
| | | | | commandline option "-i". This change fixes this and adds a test case. It also honors #include_next, although this is probably never used for embedded SQL.
* Message tuningPeter Eisentraut2010-03-21
|
* Fixed ecpg parser to allow more than one C preprocessor command inside a ↵Michael Meskes2010-03-20
| | | | declare section.
* Further corrections of mismatching struct and btree SizeOf macros.Simon Riggs2010-03-20
| | | | | In this case, correction is to remove now unused fields from struct. Since these were unused and full of garbage anyway, no version change.
* Clear error_context_stack and debug_query_string at the beginning of proc_exit,Tom Lane2010-03-20
| | | | | | | | | | | | | so that we won't try to attach any context printouts to messages that get emitted while exiting. Per report from Dennis Koegel, the context functions won't necessarily work after we've started shutting down the backend, and it seems possible that debug_query_string could be pointing at freed storage as well. The context information doesn't seem particularly relevant to such messages anyway, so there's little lost by suppressing it. Back-patch to all supported branches. I can only demonstrate a crash with log_disconnections messages back to 8.1, but the risk seems real in 8.0 and before anyway.
* Forbid renaming columns of objects whose column names are system-generated.Robert Haas2010-03-20
| | | | KaiGai Kohei, with adjustments to the comments.
* Modify error context callback functions to not assume that they can fetchTom Lane2010-03-19
| | | | | | | | | | | | | | | | | | catalog entries via SearchSysCache and related operations. Although, at the time that these callbacks are called by elog.c, we have not officially aborted the current transaction, it still seems rather risky to initiate any new catalog fetches. In all these cases the needed information is readily available in the caller and so it's just a matter of a bit of extra notation to pass it to the callback. Per crash report from Dennis Koegel. I've concluded that the real fix for his problem is to clear the error context stack at entry to proc_exit, but it still seems like a good idea to make the callbacks a bit less fragile for other cases. Backpatch to 8.4. We could go further back, but the patch doesn't apply cleanly. In the absence of proof that this fixes something and isn't just paranoia, I'm not going to expend the effort.
* Fix oversight in btpo.xact patch; it was in fact installing garbageTom Lane2010-03-19
| | | | | in the xact field on replay, due to not writing out all the data in the wal log struct.
* Add connection messages for streaming replication. log_connectionsSimon Riggs2010-03-19
| | | | | | | was broken for a replication connection and no messages were displayed on either standby or primary, at any debug level. Connection messages needed to diagnose session drop/reconnect events. Use LOG mode for now, discuss lowering in later releases.
* Minor tweaks on libpqrcv_connect(): ensure conninfo_repl[] isSimon Riggs2010-03-19
| | | | | correctly sized and expand comment to explain otherwise undocumented use of replication connection parameter.
* Update XLOG_PAGE_MAGIC to recognise WAL format changes.Simon Riggs2010-03-19
|
* Adjust comment in .history file to match recovery target specified. CommentSimon Riggs2010-03-19
| | | | | | | | 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.
* Reset btpo.xact following recovery of btree delete page. Add btpo_xactSimon Riggs2010-03-19
| | | | | | | 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.
* Also print the libpq error message when lo_create or lo_open failsPeter Eisentraut2010-03-18
|
* Prevent the injection of invalidly encoded strings by PL/Python into PostgreSQLPeter Eisentraut2010-03-18
| | | | with a few strategically placed pg_verifymbstr calls.
* Message style tuningPeter Eisentraut2010-03-18
|
* Mention way to get commit details for release notes.Bruce Momjian2010-03-18
|
* Use data-type specific conversion functions also in plpy.executePeter Eisentraut2010-03-18
| | | | | | | | | | 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.
* Add restartpoint_command option to recovery.conf. Fix bug in %r handlingHeikki Linnakangas2010-03-18
| | | | | | | | | 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.
* Add vacuum_defer_cleanup_age to postgresql.conf.sample.Simon Riggs2010-03-18
|
* Message style tuningPeter Eisentraut2010-03-17
|
* Fix peculiar, untranslatable message concatenation attemptPeter Eisentraut2010-03-17
|
* Pass incompletely-transformed aggregate argument lists as separate parametersTom Lane2010-03-17
| | | | | | 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.
* Throw a nicer error message if a standby server attempts to connect whileHeikki Linnakangas2010-03-16
| | | | | | the master is still in recovery. We don't support cascading slaves yet. Patch by Fujii Masao, with slightly changed wording.
* Remove incorrect comment from GetWriteRecPtr(): the return value is alwaysSimon Riggs2010-03-15
| | | | correct, as described in comments at start of xlog.c
* Update oidjoins regression test for 9.0.Tom Lane2010-03-14
|
* Revert all keepalive moves, reevaluate.Bruce Momjian2010-03-13
|
* Move more tcp keepalive macros to be consistent.Bruce Momjian2010-03-13
|
* Move TCP keepalive macro definitionBruce Momjian2010-03-13
| | | | Jaime Casanova
* Add libpq warning message if the .pgpass-retrieved password fails.Bruce Momjian2010-03-13
| | | | Add ERRCODE_INVALID_PASSWORD sqlstate error code.
* Allow underscores in tsearch email addressses, per RFC 5322 and reportBruce Momjian2010-03-13
| | | | | | by Dan O'Hara. Patch by Teodor Sigaev
* Small adjustment by pgindent.Bruce Momjian2010-03-13
|
* Add some logging code for unexpected cases in pgstat.c, particularly beingTom Lane2010-03-12
| | | | | | | | | | 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.
* Fix a commented-out block of code that pgindent didn't understandTom Lane2010-03-12
| | | | properly; it's been making that comment uglier with each run.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 03:12:03 +0000