aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Improve patternsel() by applying the operator itself to each valueTom Lane2006-01-10
| | | | | | | | | listed in the column's most-common-values statistics entry. This gives us an exact selectivity result for the portion of the column population represented by the MCV list, which can be a big leg up in accuracy if that's a large fraction of the population. The heuristics involving pattern contents and prefix are applied only to the part of the population not included in the MCV list.
* remove unneeded defines for uid_t and gid_t, which conflict with perl's ↵Andrew Dunstan2006-01-10
| | | | typedefs.
* In PLy_function_build_args(), the code loops repeatedly, constructingNeil Conway2006-01-10
| | | | | | | | | | | | | | | | one argument at a time and then inserting the argument into a Python list via PyList_SetItem(). This "steals" the reference to the argument: that is, the reference to the new list member is now held by the Python list itself. This works fine, except if an elog occurs. This causes the function's PG_CATCH() block to be invoked, which decrements the reference counts on both the current argument and the list of arguments. If the elog happens to occur during the second or subsequent iteration of the loop, the reference count on the current argument will be decremented twice. The fix is simple: set the local pointer to the current argument to NULL immediately after adding it to the argument list. This ensures that the Py_XDECREF() in the PG_CATCH() block doesn't double-decrement.
* Done:Bruce Momjian2006-01-09
| | | | | < * %Allow pooled connections to list all prepared statements > * -%Allow pooled connections to list all prepared statements
* Fix pg_dump to add the required OPERATOR() decoration to schema-qualifiedTom Lane2006-01-09
| | | | | | operator names. This is needed when dumping operator definitions that have COMMUTATOR (or similar) links to operators in other schemas. Apparently Daniel Whitter is the first person ever to try this :-(
* Change allow_system_table_mods to PGC_POSTMASTER, restoring previousPeter Eisentraut2006-01-09
| | | | behavior.
* Minor code cleanup for PL/Python: fixup some strangely formatted comments,Neil Conway2006-01-09
| | | | | and change two elogs into ereports because they could actually occur in practice.
* Rationalise perl header inclusions via a common include file, which alsoAndrew Dunstan2006-01-08
| | | | | | declares routines in plperl.c and spi_internal.c used in other files. Along the way, also stop perl from hijacking stdio and other stuff on Windows.
* Fix the assert_enabled issue properly. This eliminates the former ABITom Lane2006-01-08
| | | | | difference between USE_ASSERT_CHECKING and not: the assert_enabled variable is always there.
* Recent patch broke guc.c for non-USE_ASSERT_CHECKING case. PerTom Lane2006-01-08
| | | | Stefan Kaltenbrunner.
* Avoid leaking memory while reading toasted entries from pg_rewrite,Tom Lane2006-01-08
| | | | | | | and nail a couple more system indexes into cache. This doesn't make any difference in normal system operation, but when forcing constant cache resets it's difficult to get through the rules regression test without these changes.
* Add a new system view, pg_prepared_statements, that can be used toNeil Conway2006-01-08
| | | | | | | | | | | | | | | | access information about the prepared statements that are available in the current session. Original patch from Joachim Wieland, various improvements by Neil Conway. The "statement" column of the view contains the literal query string sent by the client, without any rewriting or pretty printing. This means that prepared statements created via SQL will be prefixed with "PREPARE ... AS ", whereas those prepared via the FE/BE protocol will not. That is unfortunate, but discussion on -patches did not yield an efficient way to improve this, and there is some merit in returning exactly what the client sent to the backend. Catalog version bumped, regression tests updated.
* Add RelationOpenSmgr() calls to ensure rd_smgr is valid when we try toTom Lane2006-01-07
| | | | | | use it. While it normally has been opened earlier during btree index build, testing shows that it's possible for the link to be closed again if an sinval reset occurs while the index is being built.
* Add comment explaining why RelationOpenSmgr() call is not needed.Tom Lane2006-01-07
|
* During CatCacheRemoveCList, we must now remove any members that areTom Lane2006-01-07
| | | | | | | | | dead and have become unreferenced. Before 8.1, such members were left for AtEOXact_CatCache() to clean up, but now AtEOXact_CatCache isn't supposed to have anything to do. In an assert-enabled build this bug leads to an assertion failure at transaction end, but in a non-assert build the dead member is effectively just a small memory leak. Per report from Jeremy Drake.
* Fix failure to apply domain constraints to a NULL constant that's added toTom Lane2006-01-06
| | | | an INSERT target list during rule rewriting. Per report from John Supplee.
* Use RELKIND_COMPOSITE_TYPE rather than hardcoded 'c'.Bruce Momjian2006-01-06
|
* Release-note updates and copy editing.Tom Lane2006-01-06
|
* Fix Windows-only postmaster code to reject a connection request and continue,Tom Lane2006-01-06
| | | | | | | rather than elog(FATAL), when there is no more room in ShmemBackendArray. This is a security issue since too many connection requests arriving close together could cause the postmaster to shut down, resulting in denial of service. Reported by Yoshiyuki Asaba, fixed by Magnus Hagander.
* Fix broken markup.Tom Lane2006-01-06
|
* Convert Assert checking for empty page into a regular test and elog.Tom Lane2006-01-06
| | | | | The consequences of overwriting a non-empty page are bad enough that we should not omit this test in production builds.
* Fix ReadBuffer() to correctly handle the case where it's trying to extendTom Lane2006-01-06
| | | | | | | | | the relation but it finds a pre-existing valid buffer. The buffer does not correspond to any page known to the kernel, so we *must* do smgrextend to ensure that the space becomes allocated. The 7.x branches all do this correctly, but the corner case got lost somewhere during 8.0 bufmgr rewrites. (My fault no doubt :-( ... I think I assumed that such a buffer must be not-BM_VALID, which is not so.)
* Add:Bruce Momjian2006-01-05
| | | | | > > * Allow SERIAL sequences to inherit permissions from the base table?
* Add logging control TODO.detail.Bruce Momjian2006-01-05
|
* Update:Bruce Momjian2006-01-05
| | | | | < stable logging probably can not have indexes. [wallog] > stable logging probably can not have indexes. [walcontrol]
* Update wording:Bruce Momjian2006-01-05
| | | | | | | < STABLE | DEFAULT ]. [wallog] > STABLE | DEFAULT ]. Tables using non-default logging should not use > referential integrity with default-logging tables, and tables using > stable logging probably can not have indexes. [wallog]
* Update wording:Bruce Momjian2006-01-05
| | | | | | | | | | | | < the table. Another option is to avoid transaction logging entirely < and truncate or drop the table on crash recovery. These should be < implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | < TRUNCATE | STABLE | DEFAULT ]. [wallog] > the table. This would affect COPY, and perhaps INSERT/UPDATE too. > Another option is to avoid transaction logging entirely and truncate > or drop the table on crash recovery. These should be implemented > using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE | > STABLE | DEFAULT ]. [wallog]
* Add:Bruce Momjian2006-01-05
| | | | | | | | | | | | | > > * Allow control over which tables are WAL-logged > > Allow tables to bypass WAL writes and just fsync() dirty pages on > commit. To do this, only a single writer can modify the table, and > writes must happen only on new pages. Readers can continue accessing > the table. Another option is to avoid transaction logging entirely > and truncate or drop the table on crash recovery. These should be > implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | > TRUNCATE | STABLE | DEFAULT ]. [wallog]
* Update x86 Solaris documenation ideas.Bruce Momjian2006-01-05
|
* Add compile flags sample.Bruce Momjian2006-01-05
|
* New pgcrypto item wording.Bruce Momjian2006-01-05
|
* Update item:Bruce Momjian2006-01-05
| | | | | | < * %Remove behavior of postmaster -o after making postmaster/postgres < flags unique > * %Remove behavior of postmaster -o
* Wording improvements.Bruce Momjian2006-01-05
|
* Improve markup.Bruce Momjian2006-01-05
|
* Make all command-line options of postmaster and postgres the same. SeePeter Eisentraut2006-01-05
| | | | | http://archives.postgresql.org/pgsql-hackers/2006-01/msg00151.php for the complete plan.
* Update release notes for 8.1.X, 8.0.X, 7.4.X, and 7.3.X.Bruce Momjian2006-01-05
|
* Update version number.Bruce Momjian2006-01-05
|
* Done:Bruce Momjian2006-01-05
| | | | > * -Remove BeOS and QNX-specific code
* Remove BEOS port.Bruce Momjian2006-01-05
|
* Remove QNX file.Bruce Momjian2006-01-05
|
* Remove QNX port.Bruce Momjian2006-01-05
|
* Rearrange backend startup sequence so that ShmemIndexLock can becomeTom Lane2006-01-04
| | | | | | an LWLock instead of a spinlock. This hardly matters on Unix machines but should improve startup performance on Windows (or any port using EXEC_BACKEND). Per previous discussion.
* Fix another case in which autovacuum would fail while analyzingTom Lane2006-01-04
| | | | expressional indexes. Per report from Brian Hirt.
* There is a signedness bug in Openwall gen_salt code that pgcrypto uses.Tom Lane2006-01-03
| | | | | | | This makes the salt space for md5 and xdes algorithms a lot smaller than it should be. Marko Kreen
* When the remote query result has a different number of columnsJoe Conway2006-01-03
| | | | | | than the local query specifies (e.g. in the FROM clause), throw an ERROR (instead of crashing). Fix for bug #2129 reported by Akio Iwaasa.
* Fix incorrect treatment of RL_PROMPT_START_IGNORE/RL_PROMPT_END_IGNORE,Tom Lane2006-01-03
| | | | per http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343616 via Martin Pitt.
* Add checks to verify that a plpgsql function returning a rowtype is actuallyTom Lane2006-01-03
| | | | | returning the rowtype it's supposed to return. Per reports from David Niblett and Michael Fuhr.
* Assume select() might modify struct timeout, so remove previousBruce Momjian2006-01-03
| | | | optimization.
* Use setitimer() for stats file write, rather than do a gettimeofday()Bruce Momjian2006-01-03
| | | | | call for every stats packet read to adjust select() timeout. Other stylistic improvements.
* Don't assume that LC_MESSAGES is always available on WIN32. Per Magnus.Tom Lane2006-01-02
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-07 02:57:09 +0000