aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* Add:Bruce Momjian2008-03-28
| | | | | | | | > * Allow one transaction to see tuples using the snapshot of another > transaction > > This would assist multiple backends in working together. > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00400.php
* Department of second thoughts: the rule that ORDER BY and DISTINCT areTom Lane2008-03-28
| | | | | | | | | useless for an ungrouped-aggregate query holds regardless of whether optimize_minmax_aggregates succeeds. So we might as well apply the optimization in any case. I'll leave 8.3 as it was, since this version is a tad more invasive than my earlier patch.
* Support statement-level ON TRUNCATE triggers. Simon RiggsTom Lane2008-03-28
|
* Add to TODO:Bruce Momjian2008-03-27
| | | | | | | | | > > * Consider being smarter about memory and external files used during > sorts > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg01101.php > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00045.php
* Add URL for:Bruce Momjian2008-03-27
| | | | | | | * Consider allowing control of upper/lower case folding of unquoted identifiers > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00849.php
* When we have successfully optimized a MIN or MAX aggregate into an indexscan,Tom Lane2008-03-27
| | | | | | | | | | the query result must be exactly one row (since we don't do this when there's any GROUP BY). Therefore any ORDER BY or DISTINCT attached to the query is useless and can be dropped. Aside from saving useless cycles, this protects us against problems with matching the hacked-up tlist entries to sort clauses, as seen in a bug report from Taiki Yamaguchi. We might need to work harder if we ever try to optimize grouped queries with this approach, but this solution will do for now.
* Remove ipcclean utility command --- didn't work on all Unixes and onBruce Momjian2008-03-27
| | | | Windows. Users should use their operating system tools instead.
* Sorry, copied wrong files.Michael Meskes2008-03-27
|
* - Moved from PQsetdbLogin to PQconnectDB.Michael Meskes2008-03-27
| | | | | - Correctly parse connect options. - Changed regression tests accordingly.
* Reduce the need for frontend programs to include "postgres.h" by refactoringTom Lane2008-03-27
| | | | | | | | | | | | inclusions in src/include/catalog/*.h files. The main idea here is to push function declarations for src/backend/catalog/*.c files into separate headers, rather than sticking them into the corresponding catalog definition file as has been done in the past. This commit only carries out that idea fully for pg_proc, pg_type and pg_conversion, but that's enough for the moment --- if pg_list.h ever becomes unsafe for frontend code to include, we'll need to work a bit more. Zdenek Kotala
* Move the HTSU_Result enum definition into snapshot.h, to avoid includingAlvaro Herrera2008-03-26
| | | | | | tqual.h into heapam.h. This makes all inclusion of tqual.h explicit. I also sorted alphabetically the includes on some source files.
* Rename snapmgmt.c/h to snapmgr.c/h, for consistency with other files.Alvaro Herrera2008-03-26
| | | | Per complaint from Tom Lane.
* Fix bad spelling and worse grammar in recent doc commits. PropagateTom Lane2008-03-26
| | | | pg_dump --ignore-version comments into pg_dumpall and pg_restore pages.
* Separate snapshot management code from tuple visibility code, create aAlvaro Herrera2008-03-26
| | | | | | | | | | | | | snapmgmt.c file for the former. The header files have also been reorganized in three parts: the most basic snapshot definitions are now in a new file snapshot.h, and the also new snapmgmt.h keeps the definitions for snapmgmt.c. tqual.h has been reduced to the bare minimum. This patch is just a first step towards managing live snapshots within a transaction; there is no functionality change. Per my proposal to pgsql-patches on 20080318191940.GB27458@alvh.no-ip.org and subsequent discussion.
* Include \password in the psql help.Magnus Hagander2008-03-26
| | | | | While at it, change the order of the documented options to be alphabetically again.
* Improve documentation for odd array slice behavior.Bruce Momjian2008-03-26
|
* Strengthen warnings about using pg_dump's -i option.Bruce Momjian2008-03-26
|
* Update TODO:Bruce Momjian2008-03-26
| | | | | | < o Consider invalidating the cache or keeping seperate cached < copies when search_path changes > o Consider keeping seperate cached copies when search_path changes
* Added to TODO:Bruce Momjian2008-03-26
| | | | | | | | > > * Consider transaction start/end performance improvements > > http://archives.postgresql.org/pgsql-hackers/2007-07/msg00948.php > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00361.php
* Fix core dump in contrib/xml2's xpath_table() when the input query returnsTom Lane2008-03-26
| | | | a NULL value. Per bug #4058.
* Update documentation for recent DTrace changes. Patch from Robert Lor.Neil Conway2008-03-25
|
* Simplify and standardize conversions between TEXT datums and ordinary CTom Lane2008-03-25
| | | | | | | | | | | | | | | | | | | | strings. This patch introduces four support functions cstring_to_text, cstring_to_text_with_len, text_to_cstring, and text_to_cstring_buffer, and two macros CStringGetTextDatum and TextDatumGetCString. A number of existing macros that provided variants on these themes were removed. Most of the places that need to make such conversions now require just one function or macro call, in place of the multiple notational layers that used to be needed. There are no longer any direct calls of textout or textin, and we got most of the places that were using handmade conversions via memcpy (there may be a few still lurking, though). This commit doesn't make any serious effort to eliminate transient memory leaks caused by detoasting toasted text objects before they reach text_to_cstring. We changed PG_GETARG_TEXT_P to PG_GETARG_TEXT_PP in a few places where it was easy, but much more could be done. Brendan Jurd and Tom Lane
* Done:Bruce Momjian2008-03-25
| | | | > * -Avoid tuple some tuple copying in sort routines
* Add a new tuplestore API function, tuplestore_putvalues(). This isNeil Conway2008-03-25
| | | | | | | identical to tuplestore_puttuple(), except it operates on arrays of Datums + nulls rather than a fully-formed HeapTuple. In several places that use the tuplestore API, this means we can avoid creating a HeapTuple altogether, saving a copy.
* Update TODO wording:Bruce Momjian2008-03-25
| | | | * Simplify integer cross-data-type operators
* Reword Win32 rint() item, per Tom.Alvaro Herrera2008-03-25
|
* Add URLs to previous discussions, per Simon.Alvaro Herrera2008-03-25
|
* added ECPGget_PGconn to exports.txtMichael Meskes2008-03-25
|
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | | > > * Add SQL-standard array_agg() and unnest() array functions > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg01017.php >
* Add to pl/pgsql TODO:Bruce Momjian2008-03-25
| | | | | | | | > > o Consider invalidating the cache or keeping seperate cached > copies when search_path changes > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg01009.php
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | > > * Add more cross-data-type operators > > http://archives.postgresql.org/pgsql-bugs/2008-01/msg00189.php
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | > * Detect deadlocks involving LockBufferForCleanup() > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php
* Add to psql TODO:Bruce Momjian2008-03-25
| | | | | | | | | > > o Improve display if enums > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00826.php > >
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | > > o Fix port/rint.c to be spec-compliant > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00808.php
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | > > * Consider sorting entries before inserting into btree index > > http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | | > > * Improve detection of shared memory segments being used by other > FreeBSD jails > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00656.php
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | | | > > * Move pgfoundry's xlogdump to /contrib and have it rely more closely > on the WAL backend code > > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00035.php >
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | > > * Have resource managers report the duration of their status changes > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01468.php
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | > > * Be more aggressive about creating WAL files > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01325.php
* Add:Bruce Momjian2008-03-25
| | | | | | | > o Prevent concurrent CREATE TABLE table1 from sometimes returning > a cryptic error message > > http://archives.postgresql.org/pgsql-bugs/2007-10/msg00169.php
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | > > * Have /contrib/dblink reuse unnamed connections > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00895.php
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | > * Remove old-style routines for manipulating tuples > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00851.php
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | | > > * Create three versions of libpgport to simplify client code > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00154.php >
* Add to TODO:Bruce Momjian2008-03-25
| | | | | | | > > * Fix regular expression bug when using complex back-references > > http://archives.postgresql.org/pgsql-bugs/2007-10/msg00000.php
* Add to TODO:Bruce Momjian2008-03-24
| | | | | | | | | | > > * Allow xml arrays to be cast to other data types > > http://archives.postgresql.org/pgsql-hackers/2007-09/msg00981.php > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00231.php > http://archives.postgresql.org/pgsql-hackers/2007-11/msg00471.php >
* When a relation has been proven empty by constraint exclusion, propagate thatTom Lane2008-03-24
| | | | | | | | knowledge up through any joins it participates in. We were doing that already in some special cases but not in the general case. Also, defend against zero row estimates for the input relations in cost_mergejoin --- this fix may have eliminated the only scenario in which that can happen, but be safe. Per report from Alex Solovey.
* Use new errdetail_log() mechanism to provide a less klugy way of reportingTom Lane2008-03-24
| | | | | large numbers of dependencies on a role that couldn't be dropped. Per a comment from Alvaro.
* Fix various infelicities that have snuck into usage of errdetail() andTom Lane2008-03-24
| | | | | | friends. Avoid double translation of some messages, ensure other messages are exposed for translation (and make them follow the style guidelines), avoid unsafe passing of an unpredictable message text as a format string.
* Add to TODO:Bruce Momjian2008-03-24
| | | | | | | > > * Research reducing deTOASTing in more places > > http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php
* Adjust the recent patch for reporting of deadlocked queries so that we reportTom Lane2008-03-24
| | | | | | | | query texts only to the server log. This eliminates the issue of possible leaking of security-sensitive data in other sessions' queries. Since the log is presumed secure, we can now log the queries of all sessions involved in the deadlock, whether or not they belong to the same user as the one reporting the failure.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 04:45:07 +0000