Open Hub
Open Hub

 Settings |  Report Duplicate

0
I Use This!
Inactive

Commits : Listings

Analyzed 1 day ago. based on code collected 1 day ago.
Aug 06, 2024 — Aug 06, 2025
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
Document --version and --help options for all client applications (they all support it).
tester_123
as Bruce Momjian
More... over 15 years ago
Small corrections to message output targets in pg_ctl
Peter Eisentraut
More... over 15 years ago
Don't use O_DIRECT when writing WAL files if archiving or streaming is enabled. Bypassing the kernel cache is counter-productive in that case, because the archiver/walsender process will read from the WAL file soon after it's written, and if it's not cached the read will cause a physical read, eating I/O bandwidth available on the WAL drive.
Heikki Linnakangas
More... over 15 years ago
Forbid setval() during recovery. This prevents the PANIC reported by Erik Rijkers. Patch by Andres Freund.
Heikki Linnakangas
More... over 15 years ago
First pass over client applications documentation proofreading.
tester_123
as Bruce Momjian
More... over 15 years ago
Remove mention that binary distributions pre-compile the tutorial files.
tester_123
as Bruce Momjian
More... over 15 years ago
Fix STOP WAL LOCATION in backup history files no to return the next segment of XLOG_BACKUP_END record even if the the record is placed at a segment boundary. Furthermore the previous implementation could return nonexistent segment file name when the boundary is in segments that has "FE" suffix; We never use segments with "FF" suffix.
Itagaki Takahiro
More... over 15 years ago
Translation updates for 9.0alpha4
Peter Eisentraut
More... over 15 years ago
Preliminary release notes for 9.0alpha4
Peter Eisentraut
More... over 15 years ago
Hot Standby documentation updates
tester_123
as Bruce Momjian
More... over 15 years ago
Volatile-ize all five places where we expect a PG_TRY block to restore old memory context in plpython. Before only one of them was marked volatile, but per report from Zdenek Kotala, some compilers do the wrong thing here.
tester_123
as Tom Lane
More... over 15 years ago
Provide some rather hokey ways for EXPLAIN to print FieldStore and assignment ArrayRef expressions that are not in the immediate context of an INSERT or UPDATE targetlist. Such cases never arise in stored rules, so ruleutils.c hadn't tried to handle them. However, they do occur in the targetlists of plans derived from such statements, and now that EXPLAIN VERBOSE tries to print targetlists, we need some way to deal with the case.
tester_123
as Tom Lane
More... over 15 years ago
Fix ExecEvalArrayRef to pass down the old value of the array element or slice being assigned to, in case the expression to be assigned is a FieldStore that would need to modify that value. The need for this was foreseen some time ago, but not implemented then because we did not have arrays of composites. Now we do, but the point evidently got overlooked in that patch. Net result is that updating a field of an array element doesn't work right, as illustrated if you try the new regression test on an unpatched backend. Noted while experimenting with EXPLAIN VERBOSE, which has also got some issues in this area.
tester_123
as Tom Lane
More... over 15 years ago
Fix pq_getbyte_if_available() function. It was confused on what it returns if no data is immediately available. Patch by me with numerous fixes from Fujii Masao and Magnus Hagander.
Heikki Linnakangas
More... over 15 years ago
date_recv should accept infinities.
Itagaki Takahiro
More... over 15 years ago
Add missing close tag.
tester_123
as Bruce Momjian
More... over 15 years ago
Wordsmithing of HS and SR documentation, with some wording improvements from Erik Rijkers too.
tester_123
as Bruce Momjian
More... over 15 years ago
Force READY portals into FAILED state when a transaction or subtransaction is aborted, if they were created within the failed xact. This prevents ExecutorEnd from being run on them, which is a good idea because they may contain references to tables or other objects that no longer exist. In particular this is hazardous when auto_explain is active, but it's really rather surprising that nobody has seen an issue with this before. I'm back-patching this to 8.4, since that's the first version that contains auto_explain or an ExecutorEnd hook, but I wonder whether we shouldn't back-patch further.
tester_123
as Tom Lane
More... over 15 years ago
Fix up pg_dump's treatment of large object ownership and ACLs. We now emit a separate archive entry for each BLOB, and use pg_dump's standard methods for dealing with its ownership, ACL if any, and comment if any. This means that switches like --no-owner and --no-privileges do what they're supposed to. Preliminary testing says that performance is still reasonable even with many blobs, though we'll have to see how that shakes out in the field.
tester_123
as Tom Lane
More... over 15 years ago
Take care to reprocess an uncommitted notify message.
tester_123
as Tom Lane
More... over 15 years ago
Another typo fix.
Magnus Hagander
More... over 15 years ago
Use a fatal warning check with what looks like a more portable error message. Error noticed by Tom and buildfarm member kite.
Andrew Dunstan
More... over 15 years ago
Stamp HEAD as 9.0devel, and update various places that were referring to 8.5 (hope I got 'em all). Per discussion, this release will be 9.0 not 8.5.
tester_123
as Tom Lane
More... over 15 years ago
Support new syntax and improve handling of parentheses in psql tab-completion.
Itagaki Takahiro
More... over 15 years ago
When updating ShmemVariableCache from a checkpoint record, be sure to set all the values derived from oldestXid, not just that field. Brain fade in one of my patches associated with flat file removal, exposed by a report from Fujii Masao.
tester_123
as Tom Lane
More... over 15 years ago
Prevent #option dump from crashing on FORI statement with null step. Reported by Pavel.
tester_123
as Tom Lane
More... over 15 years ago
log_error_verbosity is now LOGGING_WHAT category.
tester_123
as Tom Lane
More... over 15 years ago
Tweak description of payload parameter.
tester_123
as Tom Lane
More... over 15 years ago
Make NOTIFY_PAYLOAD_MAX_LENGTH depend explicitly on BLCKSZ and NAMEDATALEN, so this code doesn't go nuts with smaller than default BLCKSZ or larger than default NAMEDATALEN. The standard value is still exactly 8000.
tester_123
as Tom Lane
More... over 15 years ago
Replace the pg_listener-based LISTEN/NOTIFY mechanism with an in-memory queue. In addition, add support for a "payload" string to be passed along with each notify event.
tester_123
as Tom Lane
More... over 15 years ago