aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Fix mishandling of whole-row Vars referencing a view or sub-select.Tom Lane2010-06-21
| | | | | | | | 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.
* Clean up some randomness associated with trace_recovery_messages: don'tTom Lane2010-06-17
| | | | | put the variable declaration in the middle of a bunch of externs, and do use extern where it should be used.
* Make RemoveOldXlogFiles's debug printout match style used elsewhere:Tom Lane2010-06-17
| | | | | log and seg aren't an XLogRecPtr and shouldn't be printed like one. Fujii Masao
* Don't allow walsender to send WAL data until it's been safely fsync'd on theTom Lane2010-06-17
| | | | | | | | master. Otherwise a subsequent crash could cause the master to lose WAL that has already been applied on the slave, resulting in the slave being out of sync and soon corrupt. Per recent discussion and an example from Robert Haas. Fujii Masao
* Remove prototype of GetOldestWALSendPointer(), that is marked as NOT_USED.Itagaki Takahiro2010-06-17
|
* Remove perl symbol table additions for plperl functions, and mention of itAndrew Dunstan2010-06-16
| | | | in the release notes, as it is not apparently providing anything useful.
* Refactor sprintf calls with computed format strings into multiple calls withPeter Eisentraut2010-06-16
| | | | | constant format strings, so that the compiler can more easily check the formats for correctness.
* Unbreak MSVC builds for pg_archivecleanup by linking with libpgportAndrew Dunstan2010-06-15
|
* Add new GUC categories corresponding to sections in docs, and moveItagaki Takahiro2010-06-15
| | | | | | | description for vacuum_defer_cleanup_age to the correct category. Sections in postgresql.conf are also sorted in the same order with docs. Per gripe by Fujii Masao, suggestion by Heikki Linnakangas, and patch by me.
* Fix typo in Japanese translation for psql "Use \d+ to list them."Itagaki Takahiro2010-06-14
|
* If a corrupt WAL record is received by streaming replication, disconnectHeikki Linnakangas2010-06-14
| | | | | | | and retry. If the record is genuinely corrupt in the master database, there's little hope of recovering, but it's better than simply retrying to apply the corrupt WAL record in a tight loop without even trying to retransmit it, which is what we used to do.
* Remove max_standby_delay message from ps display of recovery processItagaki Takahiro2010-06-14
| | | | | in waiting status. The parameter is not so interesting in ps display because it is referable in postgresql.conf.
* Fix ALTER LARGE OBJECT and GRANT ... ON LARGE OBJECT for large OIDs.Robert Haas2010-06-13
| | | | | The previous coding failed for OIDs too large to be represented by a signed integer.
* Add missing --use-existing --help mention from regression binary.Bruce Momjian2010-06-12
| | | | Jan Urba?ski
* Fix typo/bug, found by Clang compilerPeter Eisentraut2010-06-12
|
* Update Python version informationPeter Eisentraut2010-06-12
|
* Add a regression test case for bug #5497Peter Eisentraut2010-06-12
|
* Add missing 'Z' letter to getopt_long call --- the newly addedTom Lane2010-06-11
| | | | | | --analyze-only switch did not work in its short form -Z. Josh Berkus
* Use "replication" as the database name when constructing a connectionHeikki Linnakangas2010-06-11
| | | | | | | | string for a streaming replication connection. It's ignored by the server, but allows libpq to pick up the password from .pgpass where "replication" is specified as the database name. Patch by Fujii Masao per Tom's suggestion, with some wording changes by me.
* Rename restartpoint_command to archive_cleanup_command.Itagaki Takahiro2010-06-10
|
* Make TriggerFile variable static. It's not used outside xlog.c.Heikki Linnakangas2010-06-10
| | | | Fujii Masao
* Return NULL instead of 0/0 in pg_last_xlog_receive_location() andHeikki Linnakangas2010-06-10
| | | | | | pg_last_xlog_replay_location(). Per Robert Haas's suggestion, after Itagaki Takahiro pointed out an issue in the docs. Also, some wording changes in the docs by me.
* Fix quite-bogus handling of arrays in plpython datum-to-PyObjectTom Lane2010-06-10
| | | | conversion. Per bug #5497 from David Gardner.
* Quote all string values in EXPLAIN (FORMAT YAML) output.Robert Haas2010-06-10
| | | | | | | | | | | While my previous attempt seems to always produce valid YAML, it doesn't always produce YAML that means what it appears to mean, because of tokens like "0xa" and "true", which without quotes will be interpreted as integer or Boolean literals. So, instead, just quote everything that's not known to be a number, as we do for JSON. Dean Rasheed, with some changes to the comments by me.
* Remove stray word from comment.Robert Haas2010-06-09
|
* In standby mode, respect checkpoint_segments in addition toHeikki Linnakangas2010-06-09
| | | | | | | | | | | | | checkpoint_timeout to trigger restartpoints. We used to deliberately only do time-based restartpoints, because if checkpoint_segments is small we would spend time doing restartpoints more often than really necessary. But now that restartpoints are done in bgwriter, they're not as disruptive as they used to be. Secondly, because streaming replication stores the streamed WAL files in pg_xlog, we want to clean it up more often to avoid running out of disk space when checkpoint_timeout is large and checkpoint_segments small. Patch by Fujii Masao, with some minor changes by me.
* Make the walwriter close it's handle to an old xlog segment if it's no longerMagnus Hagander2010-06-09
| | | | | | | | | the current one. Not doing this would leave the walwriter with a handle to a deleted file if there was nothing for it to do for a long period of time, preventing the file from being completely removed. Reported by Tollef Fog Heen, and thanks to Heikki for some hand-holding with the patch.
* Attempt to fix EXPLAIN (FORMAT YAML) quoting to behave sanely.Robert Haas2010-06-09
| | | | | | | | | The previous code failed to quote in many cases where quoting was necessary - YAML has loads of special characters, including -:[]{},"'|*& - so quote much more aggressively, and only refrain from quoting things where it seems fairly clear that it isn't necessary. Per report from Dean Rasheed.
* Fix typo in the header comment. Per request from Masao Fujii.Tatsuo Ishii2010-06-09
|
* Avoid useless snprintf() call when update_process_title is turned off.Tom Lane2010-06-07
| | | | Fujii Masao
* Ensure default-only storage parameters for TOAST relationsItagaki Takahiro2010-06-07
| | | | | | | | | | | | | | | | | | to be initialized with proper values. Affected parameters are fillfactor, analyze_threshold, and analyze_scale_factor. Especially uninitialized fillfactor caused inefficient page usage because we built a StdRdOptions struct in which fillfactor is zero if any reloption is set for the toast table. In addition, we disallow toast.autovacuum_analyze_threshold and toast.autovacuum_analyze_scale_factor because we didn't actually support them; they are always ignored. Report by Rumko on pgsql-bugs on 12 May 2010. Analysis by Tom Lane and Alvaro Herrera. Patch by me. Backpatch to 8.4.
* Added variable handling for RETURNING clause to ecpg.Michael Meskes2010-06-04
| | | | | | | While the values were correctly returned they were not moved into C variables as they should be. Closes: #5489
* tag 9.0beta2REL9_0_BETA2Marc G. Fournier2010-06-04
|
* Adjust misleading comment in walsender.c. We try to send all WAL data that'sTom Lane2010-06-03
| | | | | been written out from shared memory, but the previous phrasing might be read to say that we send only what's been fsync'd.
* Add current WAL end (as seen by walsender, ie, GetWriteRecPtr() result)Tom Lane2010-06-03
| | | | | | | | and current server clock time to SR data messages. These are not currently used on the slave side but seem likely to be useful in future, and it'd be better not to change the SR protocol after release. Per discussion. Also do some minor code review and cleanup on walsender.c, and improve the protocol documentation.
* Translation updates for 9.0beta2Peter Eisentraut2010-06-03
|
* Fix some inconsistent quoting of wal_level values in messagesPeter Eisentraut2010-06-03
| | | | | | When referring to postgresql.conf syntax, then it's without quotes (wal_level=archive); in narrative it's with double quotes. But never single quotes.
* Add comments about definitions that may affect PG_CONTROL_VERSION,Alvaro Herrera2010-06-03
| | | | per recent unintended-initdb-forcing fiasco
* Fix reference to nonexistent configure optionPeter Eisentraut2010-06-03
| | | | --enable-ssl -> --with-openssl
* Bump PG_CONTROL_VERSION to account for the incompatible change committed ↵Tom Lane2010-06-03
| | | | earlier.
* On clean shutdown during recovery, don't warn about possible corruption.Robert Haas2010-06-03
| | | | Fujii Masao. Review by Heikki Linnakangas and myself.
* Fix obsolete comments that I neglected to update in a previous patch.Heikki Linnakangas2010-06-02
| | | | Fujii Masao
* Show schema name for REINDEX.Bruce Momjian2010-06-01
| | | | Greg Sabino Mullane
* Add error hint that PL/pgSQL "EXECUTE of SELECT ... INTO" can beBruce Momjian2010-05-31
| | | | | | performed by "EXECUTE ... INTO". Jaime Casanova
* Send all outstanding WAL before exiting when smart shutdown is requested.Heikki Linnakangas2010-05-31
| | | | | | This was broken by my previous patch to send WAL in smaller batches. Patch by Fujii Masao.
* Fix misuse of Lossy Counting (LC) algorithm in compute_tsvector_stats().Tom Lane2010-05-30
| | | | | | | | | | | | | | | | | | | We must filter out hashtable entries with frequencies less than those specified by the algorithm, else we risk emitting junk entries whose actual frequency is much less than other lexemes that did not get tabulated. This is bad enough by itself, but even worse is that tsquerysel() believes that the minimum frequency seen in pg_statistic is a hard upper bound for lexemes not included, and was thus underestimating the frequency of non-MCEs. Also, set the threshold frequency to something with a little bit of theory behind it, to wit assume that the input distribution is approximately Zipfian. This might need adjustment in future, but some preliminary experiments suggest that it's not too unreasonable. Back-patch to 8.4, where this code was introduced. Jan Urbanski, with some editorialization by Tom
* Change the notation for calling functions with named parameters fromTom Lane2010-05-30
| | | | | | | | | | | | | "val AS name" to "name := val", as per recent discussion. This patch catches everything in the original named-parameters patch, but I'm not certain that no other dependencies snuck in later (grepping the source tree for all uses of AS soon proved unworkable). In passing I note that we've dropped the ball at least once on keeping ecpg's lexer (as opposed to parser) in sync with the backend. It would be a good idea to go through all of pgc.l and see if it's in sync now. I didn't attempt that at the moment.
* Add C comment that we will have to remove an exclusion constraint checkBruce Momjian2010-05-29
| | | | | | if we ever implement '<>' index opclasses. Jeff Davis
* Abort a FETCH_COUNT-controlled query if we observe any I/O error on theTom Lane2010-05-28
| | | | | | | | output stream. This typically indicates that the user quit out of $PAGER, or that we are writing to a file and ran out of disk space. In either case we shouldn't bother to continue fetching data. Stephen Frost
* Fix oversight in the previous patch that made LIKE throw error for \ at theTom Lane2010-05-28
| | | | | | end of the pattern: the code path that handles \ just after % should throw error too. As in the previous patch, not back-patching for fear of breaking apps that worked before.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 07:30:11 +0000