aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* When executing a list of queries derived from rule expansion,Tom Lane2006-08-14
| | | | | | | | | _SPI_execute_plan's return code should reflect the type of the query that is marked canSetTag, not necessarily the last one in the list. This is arguably a bug fix, but I'm hesitant to back-patch it because it's the sort of subtle change that might break someone's code, and it's best not to do that kind of thing in point releases.
* Remove hash_destroy calls in hash_create's failure paths. As noted byTom Lane2006-08-14
| | | | | | | a Coverity warning, these are risky since the hashtable isn't necessarily fully set up yet. They're unnecessary anyway: a deletable hashtable should be in a memory context that will be cleared following elog(ERROR). Per report from Martijn van Oosterhout.
* Revert (again) GUC patch to return commented fields to their defaultBruce Momjian2006-08-14
| | | | values, due to concern about the patch.
* Get rid of "lookahead" functionality in plpgsql's yylex() function,Tom Lane2006-08-14
| | | | | | | | | | | | | | | | | | | | | | and instead make the grammar production for the RETURN statement do the heavy lifting. The lookahead idea was copied from the main parser, but it does not work in plpgsql's parser because here gram.y looks explicitly at the scanner's yytext variable, which will be out of sync after a failed lookahead step. A minimal example is create or replace function foo() returns void language plpgsql as ' begin perform return foo bar; end'; which can be seen by testing to deliver "foo foo bar" to the main parser instead of the expected "return foo bar". This isn't a huge bug since RETURN is not found in the main grammar, but it could bite someone who tried to use "return" as an identifier. Back-patch to 8.1. Bug exists further back, but HEAD patch doesn't apply cleanly, and given the lack of field complaints it doesn't seem worth the effort to develop adjusted patches.
* Fix core dump in duration logging for a V3-protocol Execute messageTom Lane2006-08-13
| | | | | | when what's being executed is a COMMIT or ROLLBACK. Per report from Sergey Koposov. Backpatch to 8.1; 8.0 and before don't have the bug due to lack of any logging at all here.
* Cause psql to report both the returned data and the command status tagTom Lane2006-08-13
| | | | for INSERT/UPDATE/DELETE RETURNING. Per discussion.
* If test postmaster fails to start within 60 seconds, try to kill -9 itTom Lane2006-08-13
| | | | | so that it won't interfere with later trials. Per recent buildfarm experience. Anyone know how to do this on Windows?
* Extend 'guc' regression test to check manipulations of datestyle asTom Lane2006-08-13
| | | | | | | | well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
* Original coding of 'returning' regression test inadvertently chose aTom Lane2006-08-13
| | | | | | nonunique join value, leading to plan-choice-dependent results ... and it seems some platforms will choose a different plan. Tweak the test so that it has well-defined results. Per report from Olivier Prenant.
* Back out plperl OUT hash/array parameter patch, again.Bruce Momjian2006-08-13
|
* Fix recent guc comment-to-default patch for custom variables.Bruce Momjian2006-08-13
|
* Applied patch for VPATH builds by Alvaro Herrera <alvherre@commandprompt.com>Michael Meskes2006-08-13
| | | | | Merged dyntest.pgc and dyntest2.pgc. Hopefully fixed the last Coverity reports (finally)
* Re-apply plperl patch that allows OUT parameters to be placed into PerlBruce Momjian2006-08-13
| | | | hash and array variables. (regression output updated)
* Recommit patch to allow commented GUC variables to return to theirBruce Momjian2006-08-13
| | | | default values.
* Re-apply guc cleanup patch, with memory allocation bugs fixed.Bruce Momjian2006-08-13
|
* Tweak SPI_cursor_open to allow INSERT/UPDATE/DELETE RETURNING; this wasTom Lane2006-08-12
| | | | | | | | merely a matter of fixing the error check, since the underlying Portal infrastructure already handles it. This in turn allows these statements to be used in some existing plpgsql and plperl contexts, such as a plpgsql FOR loop. Also, do some marginal code cleanup in places that were being sloppy about distinguishing SELECT from SELECT INTO.
* Remove ancient, obsolete comment.Tom Lane2006-08-12
|
* Back out patch for plperl to handle OUT paramaters into arrays andBruce Momjian2006-08-12
| | | | hashes. Was causing regression failures.
* Back out patch to reorganize guc processing. Was causing regressionBruce Momjian2006-08-12
| | | | failures.
* Back out patch that allowed commented guc variables to return to theirBruce Momjian2006-08-12
| | | | default values. Was causing regression failures.
* Add INSERT/UPDATE/DELETE RETURNING, with basic docs and regression tests.Tom Lane2006-08-12
| | | | | | | | plpgsql support to come later. Along the way, convert execMain's SELECT INTO support into a DestReceiver, in order to eliminate some ugly special cases. Jonah Harris and Tom Lane
* Set Win32 server-size socket buffer to 32k, for performance reasons.Bruce Momjian2006-08-11
| | | | Yoshiyuki Asaba
* Allow commenting of variables in postgresql.conf to restore them toBruce Momjian2006-08-11
| | | | | | defaults. Zdenek Kotala
* Refactor GUC set_config_option function:Bruce Momjian2006-08-11
| | | | | | | | | | | | | | | | | | The main reason for refactoring was that set_config_option() was too overloaded function and its behavior did not consistent. Old version of set_config_function hides some messages. For example if you type: tcp_port = 5432.1 then old implementation ignore this error without any message to log file in the signal context (configuration reload). Main problem was that semantic analysis of postgresql.conf is not perform in the ProcessConfigFile function, but in the set_config_options *after* context check. This skipped check for variables with PG_POSTMASTER context. There was request from Joachim Wieland to add more messages about ignored changes in the config file as well. Zdenek Kotala
* plperl:Bruce Momjian2006-08-11
| | | | | | | Allow conversion from perl to postgresql array in OUT parameters. Second, allow hash form output from procedures with one OUT argument. Pavel Stehule
* Make the psql line counter 64-bit so it can handle files > 4gig lines.Bruce Momjian2006-08-11
| | | | David Fetter
* Fix UNION/INTERSECT/EXCEPT so that when two inputs being merged haveTom Lane2006-08-10
| | | | | | | same data type and same typmod, we show that typmod as the output typmod, rather than generic -1. This responds to several complaints over the past few years about UNIONs unexpectedly dropping length or precision info.
* Return inline to win32.h because code was OK, but keep additionalBruce Momjian2006-08-10
| | | | comment. 8.1.X is not affected by this commit.
* Move "#define inline __inline" from port/win32.h to c.h because Win32Bruce Momjian2006-08-10
| | | | | | interface builds like libpq need it. Backpatch addition to 8.1.X.
* Fix display of log duration so it is milliseconds.microseconds "ms".Bruce Momjian2006-08-10
| | | | Greg Sabino Mullane
* Fix inadequate makefile-fu in ecpg regression tests. I think thisTom Lane2006-08-09
| | | | will fix current platypus build failure.
* Round microseconds on setitimer upwards.Bruce Momjian2006-08-09
|
* On Win32, make minimum setitimer() sleep be 1ms, so sleeps < 1ms aren'tBruce Momjian2006-08-09
| | | | | | rounded down to zero. Backpatch to 8.1.X.
* Fix statement_timeout on Win32 so that it properly treats micro-secondsBruce Momjian2006-08-09
| | | | | | | | as micro-seconds, rather than as 100 microseconds, as it does now. This actually fixes all setitimer calls on Win32, but statement_timeout is the most visible fix. Backpatch to 8.1.X. 8.0 works as documented.
* Formatting improvement.Bruce Momjian2006-08-09
|
* Fixed some memory bugs that somehow reappeared.Michael Meskes2006-08-09
| | | | Also fixed a new Coverity report.
* Fixed error handling in numeric conversion (Joachim).Michael Meskes2006-08-09
| | | | Further regression cleanup.
* Suppress MSVC warnings about weak functions by usingBruce Momjian2006-08-09
| | | | | | _CRT_SECURE_NO_DEPRECATE. Hiroshi Saito
* Fix win32.mak for config cleanup.Bruce Momjian2006-08-08
| | | | Hiroshi Saito
* Fix 'make clean' for change of regression.diffs file name.Tom Lane2006-08-08
|
* Add a feature for automatic initialization and finalization of dynamicallyTom Lane2006-08-08
| | | | | | | | | loaded libraries: call functions _PG_init() and _PG_fini() if the library defines such symbols. Hence we no longer need to specify an initialization function in preload_libraries: we can assume that the library used the _PG_init() convention, instead. This removes one source of pilot error in use of preloaded libraries. Original patch by Ralf Engelschall, preload_libraries changes by me.
* Fix definition of "errcode" for MSVC.Bruce Momjian2006-08-08
| | | | Hiroshi Saito
* Cleaned up log output a little bit more.Michael Meskes2006-08-08
|
* Made parser check for valid copy to/from stdin/stdout combinations.Michael Meskes2006-08-08
| | | | Lots of small changes in regression test suite
* For protocol-level prepare/bind/execute:Bruce Momjian2006-08-08
| | | | | | | | o print user name for all o print portal name if defined for all o print query for all o reduce log_statement header to single keyword o print bind parameters as DETAIL if text mode
* Put back another improperly-removed #include.Tom Lane2006-08-07
|
* On some platforms, pg_usleep isn't interruptible by signals; fixTom Lane2006-08-07
| | | | | archiver to behave per original coder's expectation on these machines. We already know this everywhere else AFAICT.
* Make recovery from WAL be restartable, by executing a checkpoint-likeTom Lane2006-08-07
| | | | | | | | | | operation every so often. This improves the usefulness of PITR log shipping for hot standby: formerly, if the standby server crashed, it was necessary to restart it from the last base backup and replay all the WAL since then. Now it will only need to reread about the same amount of WAL as the master server would. The behavior might also come in handy during a long PITR replay sequence. Simon Riggs, with some editorialization by Tom Lane.
* Joachim fixed some bugs in numeric handling in pgtypeslib.Michael Meskes2006-08-07
| | | | Fixed and cleaned up some regression tests. Also added a new one.
* Tweak sanity_check regression test to display more tables (viz, thoseTom Lane2006-08-06
| | | | | | | | without indexes) but not to display temp tables. It's a bit hard to credit that sanity_check could get through a database-wide VACUUM while the preceding create_index test is still trying to clean up its temp tables ... but I see no other explanation for the current failure report from buildfarm member sponge.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-06 05:14:52 +0000