aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Fix some misuses of strncat().Tom Lane2006-09-27
|
* Remove separate strdup.h header file; it's redundant with port.h.Tom Lane2006-09-27
|
* Degrade the transaction-id wraparound point message from LOG to DEBUG1, perAlvaro Herrera2006-09-26
| | | | | | discussion. Patch from Simon Riggs.
* Added new filesMichael Meskes2006-09-26
|
* Added Joachim's changes for MinGW.Michael Meskes2006-09-26
| | | | Added SET DATESTYLE to one test so the output format is defined.
* Increase default value of effective_cache_size to 128MB, per discussion.Tom Lane2006-09-25
|
* Add a check to prevent overwriting valid data if smgrnblocks() gives aTom Lane2006-09-25
| | | | | | wrong answer, as has been seen to occur with a buggy Linux kernel. Not really our bug, but it's a simple test in a seldom-used control path, so might as well have a defense.
* Fix notice message from DROP FUNCTION IF EXISTS, and improve messageTom Lane2006-09-25
| | | | for DROP AGGREGATE IF EXISTS. Per report from Teodor.
* Fix incorrect mapping of fopen mode 'a' in recently-added code toTom Lane2006-09-24
| | | | make fopen work safely on Windows. Magnus
* Cause pg_regress to invoke the temporary postmaster as 'postgres' notTom Lane2006-09-24
| | | | | | 'postmaster', so as not to depend on the existence of the postmaster symlink. Also, implement postmaster-still-alive and postmaster-kill operations for Windows, per Magnus.
* Suppress useless warning on pre-XP versions of Windows. MagnusTom Lane2006-09-24
|
* Tag us Beta1REL8_2_BETA1PostgreSQL Daemon2006-09-23
|
* Fix pg_locks view to call advisory locks advisory locks, while preservingTom Lane2006-09-22
| | | | | backward compatibility for anyone using the old userlock code that's now on pgfoundry --- locks from that code still show as 'userlock'.
* Fix bugs in plpgsql and ecpg caused by assuming that isspace() would onlyTom Lane2006-09-22
| | | | | | | | | return true for exactly the characters treated as whitespace by their flex scanners. Per report from Victor Snezhko and subsequent investigation. Also fix a passel of unsafe usages of <ctype.h> functions, that is, ye olde char-vs-unsigned-char issue. I won't miss <ctype.h> when we are finally able to stop using it.
* Surely this temp buffer needn't be static.Tom Lane2006-09-22
|
* Rearrange yes/no prompting code so that the prompts always show thePeter Eisentraut2006-09-22
| | | | | | | (possibly (un)translated) letters that are actually expected as input. Also reject invalid responses instead of silenty taken them as "no". with help from Bernd Helmle
* Add units to the default postgresql.conf. For the most part, this shouldPeter Eisentraut2006-09-22
| | | | | match what SHOW displays as default value, to make the user experience uniform.
* Fix free space map to correctly track the total amount of FSM space neededTom Lane2006-09-21
| | | | | | | even when a single relation requires more than max_fsm_pages pages. Also, make VACUUM emit a warning in this case, since it likely means that VACUUM FULL or other drastic corrective measure is needed. Per reports from Jeff Frost and others of unexpected changes in the claimed max_fsm_pages need.
* Change patternsel (LIKE/regex selectivity estimation) so that if thereTom Lane2006-09-20
| | | | | | | | | is a large enough histogram, it will use the number of matches in the histogram to derive a selectivity estimate, rather than the admittedly pretty bogus heuristics involving examining the pattern contents. I set 'large enough' at 100, but perhaps we should change that later. Also apply the same technique in contrib/ltree's <@ and @> estimator. Per discussion with Stefan Kaltenbrunner and Matteo Beccati.
* Improve usage of effective_cache_size parameter by assuming that all theTom Lane2006-09-19
| | | | | | | | | | | tables in the query compete for cache space, not just the one we are currently costing an indexscan for. This seems more realistic, and it definitely will help in examples recently exhibited by Stefan Kaltenbrunner. To get the total size of all the tables involved, we must tweak the handling of 'append relations' a bit --- formerly we looked up information about the child tables on-the-fly during set_append_rel_pathlist, but it needs to be done before we start doing any cost estimation, so push it into the add_base_rels_to_query scan.
* Fix shared library creation to work properly on AIX. Albe LaurenzTom Lane2006-09-19
|
* Add built-in userlock manipulation functions to replace the formerTom Lane2006-09-18
| | | | | | | contrib functionality. Along the way, remove the USER_LOCKS configuration symbol, since it no longer makes any sense to try to compile that out. No user documentation yet ... mmoncure has promised to write some. Thanks to Abhijit Menon-Sen for creating a first draft to work from.
* Fix problems with column name list of CREATE TABLE AS being applied toTom Lane2006-09-18
| | | | | the input query's target list too soon, causing it to affect processing of ORDER BY in the input query.
* Fix CREATE TABLE ... AS VALUES ... to work rather than Assert'ing;Tom Lane2006-09-18
| | | | | | oversight in original implementation of VALUES. Also fix an oversight in recent addition of options to CREATE TABLE AS: they weren't getting propagated if the query was a set-operation such as UNION.
* Change ANALYZE to take ShareUpdateExclusiveLock not AccessShareLock onTom Lane2006-09-17
| | | | | | | | | | | | the table being analyzed. This prevents two ANALYZEs from running concurrently on the same table and possibly suffering concurrent-update failures while trying to store their results into pg_statistic. The downside is that a database-wide ANALYZE executed within a transaction block will hold ShareUpdateExclusiveLock on many tables simultaneously, which could lead to concurrency issues or even deadlock against another such ANALYZE. However, this seems a corner case of less importance than getting unexpected errors from a foreground ANALYZE when autovacuum elects to analyze the same table concurrently. Per discussion.
* Marginal cleanup in arrangements for ensuring StrategyHintVacuum is clearedTom Lane2006-09-17
| | | | | | | | | after an error during VACUUM. We have a PG_TRY block anyway around the only call sites, so just reset it in the CATCH clause instead of having AtEOXact_Buffers blindly do it during xact end. I think the old code was actively wrong for the case of a failure during ANALYZE inside a subtransaction --- the flag wouldn't get cleared until main transaction end. Probably not worth back-patching though.
* Rename the recently-added pg_timezonenames view to pg_timezone_abbrevs,Tom Lane2006-09-16
| | | | | | and create a new view pg_timezone_names that provides information about the zones known in the 'zic' database. Magnus Hagander, with some additional work by Tom Lane.
* Update timezone data files to release 2006k of the zic database.Tom Lane2006-09-16
|
* Define errcode as __msvc_errcode not __vc_errcode for MSVC builds,Tom Lane2006-09-16
| | | | per Magnus.
* Several fixes for MSVC build scripts, from Magnus.Tom Lane2006-09-15
|
* Fix some uses of str[n]casecmp that should be pg_str[n]casecmp,Tom Lane2006-09-15
| | | | per Magnus.
* Remove WINLDAPAPI decoration from ldap_start_tls_sA typedef, per Magnus.Tom Lane2006-09-15
|
* Improve confusing comment for HeapTupleSatisfiesNow, per gripe from Greg Stark.Tom Lane2006-09-15
|
* Make postgresql.conf.sample match the initdb defaults. This fixesBruce Momjian2006-09-14
| | | | comment alignment on most systems.
* Add a couple of information functions to support direct checks on whetherTom Lane2006-09-14
| | | | | | a schema is our own temp schema or another backend's temp schema, and use these in place of some former kluges in information_schema. Per my proposal of yesterday.
* Improve error message. Per discussionTeodor Sigaev2006-09-14
| | | | http://archives.postgresql.org/pgsql-general/2006-09/msg00186.php
* Cygwin systems seem to have a different error message when trying to connect ↵Michael Meskes2006-09-14
| | | | to port 0. Let's try port 20 instead.
* Added missing constuctor/destructor for interval and date.Michael Meskes2006-09-14
|
* Make logging of extended-protocol commands a bit more consistent, perTom Lane2006-09-13
| | | | discussion with Guillaume Smet.
* Code review for patch to avoid second scan when vacuuming index-lessTom Lane2006-09-13
| | | | | table: avoid invoking LockBufferForCleanup without need, put out the same log message we would have before, minor code beautification.
* Seems this wasn't committed originallyMichael Meskes2006-09-12
|
* Move set_pglocale_pgservice() from path.c to exec.c, so that pulling inTom Lane2006-09-11
| | | | | path.c does not in itself force linking of both exec.c and libintl. Should fix current ecpglib build failure on pickier platforms.
* Add LDAP_LIBS_FE to $(libpq) for static or AIX linking, per Albe Laurenz.Tom Lane2006-09-11
|
* Ooops, forgot to update ecpg comparison files to matchTom Lane2006-09-11
| | | | source-code change.
* Fix unportable usage complained of by icc. Per buildfarm results.Tom Lane2006-09-11
|
* Remove unnecessary brace pair.Bruce Momjian2006-09-10
|
* Back out patch added during 8.2.X development:Bruce Momjian2006-09-10
| | | | | | | Allow to_char() "D" format specifiers for interval/time. It doesn't work, and I doubt it is useful enough to fix ("D" = day of week).
* Install a cleaner solution to the AIX libpq linking problem, as perTom Lane2006-09-10
| | | | | | | an earlier discussion. Centralize assumptions about what libpq depends on in one place in Makefile.global. I am unconvinced that this list is complete, but since ecpg seems to have gotten along with just these entries, we'll try it this way and see what happens.
* If we're going to advertise the array overlap/containment operators,Tom Lane2006-09-10
| | | | | | we probably should make them work reliably for all arrays. Fix code to handle NULLs and multidimensional arrays, move it into arrayfuncs.c. GIN is still restricted to indexing arrays with no null elements, however.
* Rename contains/contained-by operators to @> and <@, per discussion thatTom Lane2006-09-10
| | | | | | | | agreed these symbols are less easily confused. I made new pg_operator entries (with new OIDs) for the old names, so as to provide backward compatibility while making it pretty easy to remove the old names in some future release cycle. This commit only touches the core datatypes, contrib will be fixed separately.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 15:34:07 +0000