aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Tidy up and refactor plperl.c.Andrew Dunstan2010-01-09
| | | | | | | | | | | | | | | | | | | | | | - Changed MULTIPLICITY check from runtime to compiletime. No loads the large Config module. - Changed plperl_init_interp() to return new interp and not alter the global interp_state - Moved plperl_safe_init() call into check_interp(). - Removed plperl_safe_init_done state variable as interp_state now covers that role. - Changed plperl_create_sub() to take a plperl_proc_desc argument. - Simplified return value handling in plperl_create_sub. - Changed perl.com link in the docs to perl.org and tweaked wording to clarify that require, not use, is what's blocked. - Moved perl code in large multi-line C string literal macros out to plc_*.pl files. - Added a test2macro.pl utility to convert the plc_*.pl files to macros in a perlchunks.h file which is #included - Simplifed plperl_safe_init() slightly - Optimized pg_verifymbstr calls to avoid unneeded strlen()s. Patch from Tim Bunce, with minor editing from me.
* Also update ChangerLog file.Michael Meskes2010-01-08
|
* Fix oversight in EvalPlanQualFetch: after failing to lock a tuple becauseTom Lane2010-01-08
| | | | | | | | | | | | | | | | someone else has just updated it, we have to set priorXmax to that tuple's xmax (ie, the XID of the other xact that updated it) before looping back to examine the next tuple. Obviously, the next tuple in the update chain should have that XID as its xmin, not the same xmin as the preceding tuple that we had been trying to lock. The mismatch would cause the EvalPlanQual logic to decide that the tuple chain ended in a deletion, when actually there was a live tuple that should have been found. I inserted this error when recently adding logic to EvalPlanQual to make it lock tuples before returning them (as opposed to the old method in which the lock would occur much later, causing a great deal of work to be wasted if we only then discover someone else updated it). Sigh. Per today's report from Takahiro Itagaki of inconsistent results during pgbench runs.
* pgBufferUsage needs PGDLLIMPORT for pg_stat_statements on Windows.Itagaki Takahiro2010-01-08
|
* Document why we copy reloptions into CacheMemoryContext after-the-fact.Robert Haas2010-01-07
|
* Fix 3-parameter form of bit substring() to throw error for negative length,Tom Lane2010-01-07
| | | | as required by SQL standard.
* Make bit/varbit substring() treat any negative length as meaning "all the restTom Lane2010-01-07
| | | | | | | | | | | of the string". The previous coding treated only -1 that way, and would produce an invalid result value for other negative values. We ought to fix it so that 2-parameter bit substring() is a different C function and the 3-parameter form throws error for negative length, but that takes a pg_proc change which is impractical in the back branches; and in any case somebody might be relying on -1 working this way. So just do this as a back-patchable fix.
* Fix (some of the) breakage introduced into query-cancel processing by HS.Tom Lane2010-01-07
| | | | | | | | | | | | | | It is absolutely not okay to throw an ereport(ERROR) in any random place in the code just because DoingCommandRead is set; interrupting, say, OpenSSL in the midst of its activities is guaranteed to result in heartache. Instead of that, undo the original optimizations that threw away QueryCancelPending anytime we were starting or finishing a command read, and instead discard the cancel request within ProcessInterrupts if we find that there is no HS reason for forcing a cancel and we are DoingCommandRead. In passing, may I once again condemn the practice of changing the code and not fixing the adjacent comment that you just turned into a lie?
* Use -Z for vacuumdb --analyze-only, rather than -o.Bruce Momjian2010-01-07
|
* Rename new vacuumdb option to --analyze-only from --only-analyze.Bruce Momjian2010-01-07
|
* Remove all the special-case code for INT64_IS_BUSTED, per decision thatTom Lane2010-01-07
| | | | | | | | we're not going to support that anymore. I did keep the 64-bit-CRC-with-32-bit-arithmetic code, since it has a performance excuse to live. It's a bit moot since that's all ifdef'd out, of course.
* More tablespace.c comment improvements.Bruce Momjian2010-01-07
|
* Clarify tablespace.c::TablespaceCreateDbspace() comments.Bruce Momjian2010-01-07
|
* Further fixes for per-tablespace options patch.Robert Haas2010-01-07
| | | | | | | Add missing varlena header to TableSpaceOpts structure. And, per Tom Lane, instead of calling tablespace_reloptions in CacheMemoryContext, call it in the caller's memory context and copy the value over afterwards, to reduce the chances of a session-lifetime memory leak.
* Improve a couple of comments relating to large object snapshot management.Robert Haas2010-01-07
|
* Alter the configure script to fail immediately if the C compiler does notTom Lane2010-01-07
| | | | | | | | | | | | | | provide a working 64-bit integer datatype. As recently noted, we've been broken on such platforms since early in the 8.4 development cycle. Since it took nearly two years for anyone to even notice, it seems that the rationale for continuing to support such platforms has reached the point of non-existence. Rather than thrashing around to try to make it work again, we'll just admit up front that this no longer works. Back-patch to 8.4 since that branch is also broken. We should go around to remove INT64_IS_BUSTED support, but just in HEAD, so that seems like material for a separate commit.
* PG_MAJORVERSION:Bruce Momjian2010-01-06
| | | | | For simplicity, use PG_MAJORVERSION rather than PG_VERSION for creation of the PG_VERSION file.
* Fix spccache.c to not suppose that a cache entry will live across databaseTom Lane2010-01-06
| | | | access, per testing with CLOBBER_CACHE_ALWAYS. Minor other editorialization.
* Access hash entry before freeing it, not after.Tom Lane2010-01-06
|
* Make error messages for bad --set-version argument more useful.Tom Lane2010-01-06
| | | | Per Stefan.
* Make the makefile pass $MAJORVERSION to genbki.pl, not $VERSION which isTom Lane2010-01-06
| | | | | overridden in the snapshot build script. $MAJORVERSION is what it really wanted anyway, so we can tighten up the parsing of --set-version's argument.
* Corrected CVS entry:Bruce Momjian2010-01-06
| | | | --only-analyze mode is for _vacuumdb_, not pg_dump.
* Replaced int64_t with int64 as Andrew suggested.Michael Meskes2010-01-06
|
* Remove __FUNCTION__ keyword that is not recognized by som compilers.Michael Meskes2010-01-06
|
* Removed test case using nan as float value because printf's output for nan isMichael Meskes2010-01-06
| | | | | OS specific with some distinguishing between signaling and quiet nans. It's not really importnat for us here anyway.
* Removed more inttypes.h stuff.Michael Meskes2010-01-06
|
* Silence compiler warning about uninitialized variables. This initializationItagaki Takahiro2010-01-06
| | | | is not necessary needed, but some compilers complain about it.
* Applied Zoltan's patch to remove hardware dependant offset logging andMichael Meskes2010-01-06
| | | | superfluous include files.
* Support rewritten-based full vacuum as VACUUM FULL. TraditionalItagaki Takahiro2010-01-06
| | | | | | | | | | | VACUUM FULL was renamed to VACUUM FULL INPLACE. Also added a new option -i, --inplace for vacuumdb to perform FULL INPLACE vacuuming. Since the new VACUUM FULL uses CLUSTER infrastructure, we cannot use it for system tables. VACUUM FULL for system tables always fall back into VACUUM FULL INPLACE silently. Itagaki Takahiro, reviewed by Jeff Davis and Simon Riggs.
* binary upgrade:Bruce Momjian2010-01-06
| | | | | | | Preserve relfilenodes for views and composite types --- even though we don't store data in, them, they do consume relfilenodes. Bump catalog version.
* Remove erroneous comma added to pg_dumpall tablespace query when runningBruce Momjian2010-01-06
| | | | with PG version 8.2-8.4.
* Update catalog version for recent relfilenode patch, so pg_migrator canBruce Momjian2010-01-06
| | | | identify the new API.
* Preserve relfilenodes:Bruce Momjian2010-01-06
| | | | | Add support to pg_dump --binary-upgrade to preserve all relfilenodes, for use by pg_migrator.
* pg_dump --only-analyzeBruce Momjian2010-01-06
| | | | | Implement pg_dump --only-analyze for use by pg_migrator to only analyze all databases.
* Remove tabs in SGML.Bruce Momjian2010-01-06
| | | | Move OIDCHARS to proper include file.
* Use OIDCHARS:Bruce Momjian2010-01-06
| | | | | Use OIDCHARS for oid character length, rather than '10', in tablespace code.
* Add support for doing FULL JOIN ON FALSE. While this is really a ratherTom Lane2010-01-05
| | | | | | | | | | peculiar variant of UNION ALL, and so wouldn't likely get written directly as-is, it's possible for it to arise as a result of simplification of less-obviously-silly queries. In particular, now that we can do flattening of subqueries that have constant outputs and are underneath an outer join, it's possible for the case to result from simplification of queries of the type exhibited in bug #5263. Back-patch to 8.4 to avoid a functionality regression for this type of query.
* Support ALTER TABLESPACE name SET/RESET ( tablespace_options ).Robert Haas2010-01-05
| | | | | | | | | This patch only supports seq_page_cost and random_page_cost as parameters, but it provides the infrastructure to scalably support many more. In particular, we may want to add support for effective_io_concurrency, but I'm leaving that as future work for now. Thanks to Tom Lane for design help and Alvaro Herrera for the review.
* Fix genbki.pl and Gen_fmgrtab.pl to use PID-specific temp file names,Tom Lane2010-01-05
| | | | | so that it's safe if a parallel make chooses to run two concurrent copies. Also, work around a memory leak in some versions of Perl.
* And another oneMichael Meskes2010-01-05
|
* And another one of the same problem.Michael Meskes2010-01-05
|
* And then forgot to commit the fixed files. ARGH!Michael Meskes2010-01-05
|
* Ah, should read the file completely. I got so used to git that I almost ↵Michael Meskes2010-01-05
| | | | forgot about the cvs stuff.
* Thrid try. It seems my two checkouts need some cleaning up.Michael Meskes2010-01-05
|
* Still not correct.Michael Meskes2010-01-05
|
* Adjusted CVS headers.Michael Meskes2010-01-05
|
* Applied patch by Boszormenyi Zoltan <zb@cybertec.at> to add sqlda support toMichael Meskes2010-01-05
| | | | ecpg in both native and compatiblity mode.
* Move the default configuration for the MSVC build system to config_default.pl,Magnus Hagander2010-01-05
| | | | | | | | | | and allow using config.pl to override the defaults. config.pl is removed from the repository, so changes there will no longer show up when doing diff, and will not prevent switching branches and such things. config.pl would normally be used to override single values, but if an old-style config.pl is read, it will override the entire default configuration, making it backwards compatible.
* Disable linker warning 4197 on Win64, that is caused by the fact that we exportMagnus Hagander2010-01-05
| | | | | | | | | symbols both using __declspec(dllexport) (via the PGDLLIMPORT macro) and using full-dll-export. This works without warning on Win32, but not on Win64. In passing, fix the fact that the framework could never deal with more than one disbled linker warning - because MSVC wants commas between linker warnings, and semicolons between compiler warnings...
* Use _mm_pause() for win64 spin_delay(), per note from Tsutomu Yamada.Magnus Hagander2010-01-05
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-16 03:00:59 +0000