summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2008-03-28Add to TODO:Bruce Momjian
> > o Add CASE capability to language (already in SQL) > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00696.php > >
2008-03-28Add:Bruce Momjian
> * 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
2008-03-28Department of second thoughts: the rule that ORDER BY and DISTINCT areTom Lane
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.
2008-03-28Support statement-level ON TRUNCATE triggers. Simon RiggsTom Lane
2008-03-27Add to TODO:Bruce Momjian
> > * 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
2008-03-27Add URL for:Bruce Momjian
* Consider allowing control of upper/lower case folding of unquoted identifiers > http://archives.postgresql.org/pgsql-hackers/2008-03/msg00849.php
2008-03-27When we have successfully optimized a MIN or MAX aggregate into an indexscan,Tom Lane
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.
2008-03-27Remove ipcclean utility command --- didn't work on all Unixes and onBruce Momjian
Windows. Users should use their operating system tools instead.
2008-03-27Sorry, copied wrong files.Michael Meskes
2008-03-27- Moved from PQsetdbLogin to PQconnectDB.Michael Meskes
- Correctly parse connect options. - Changed regression tests accordingly.
2008-03-27Reduce the need for frontend programs to include "postgres.h" by refactoringTom Lane
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
2008-03-26Move the HTSU_Result enum definition into snapshot.h, to avoid includingAlvaro Herrera
tqual.h into heapam.h. This makes all inclusion of tqual.h explicit. I also sorted alphabetically the includes on some source files.
2008-03-26Rename snapmgmt.c/h to snapmgr.c/h, for consistency with other files.Alvaro Herrera
Per complaint from Tom Lane.
2008-03-26Fix bad spelling and worse grammar in recent doc commits. PropagateTom Lane
pg_dump --ignore-version comments into pg_dumpall and pg_restore pages.
2008-03-26Separate snapshot management code from tuple visibility code, create aAlvaro Herrera
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.
2008-03-26Include \password in the psql help.Magnus Hagander
While at it, change the order of the documented options to be alphabetically again.
2008-03-26Improve documentation for odd array slice behavior.Bruce Momjian
2008-03-26Strengthen warnings about using pg_dump's -i option.Bruce Momjian
2008-03-26Update TODO:Bruce Momjian
< o Consider invalidating the cache or keeping seperate cached < copies when search_path changes > o Consider keeping seperate cached copies when search_path changes
2008-03-26Added to TODO:Bruce Momjian
> > * 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
2008-03-26Fix core dump in contrib/xml2's xpath_table() when the input query returnsTom Lane
a NULL value. Per bug #4058.
2008-03-25Update documentation for recent DTrace changes. Patch from Robert Lor.Neil Conway
2008-03-25Simplify and standardize conversions between TEXT datums and ordinary CTom Lane
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
2008-03-25Done:Bruce Momjian
> * -Avoid tuple some tuple copying in sort routines
2008-03-25Add a new tuplestore API function, tuplestore_putvalues(). This isNeil Conway
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.
2008-03-25Update TODO wording:Bruce Momjian
* Simplify integer cross-data-type operators
2008-03-25Reword Win32 rint() item, per Tom.Alvaro Herrera
2008-03-25Add URLs to previous discussions, per Simon.Alvaro Herrera
2008-03-25added ECPGget_PGconn to exports.txtMichael Meskes
2008-03-25Add to TODO:Bruce Momjian
> > * Add SQL-standard array_agg() and unnest() array functions > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg01017.php >
2008-03-25Add to pl/pgsql TODO:Bruce Momjian
> > o Consider invalidating the cache or keeping seperate cached > copies when search_path changes > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg01009.php
2008-03-25Add to TODO:Bruce Momjian
> > * Add more cross-data-type operators > > http://archives.postgresql.org/pgsql-bugs/2008-01/msg00189.php
2008-03-25Add to TODO:Bruce Momjian
> * Detect deadlocks involving LockBufferForCleanup() > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00873.php
2008-03-25Add to psql TODO:Bruce Momjian
> > o Improve display if enums > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00826.php > >
2008-03-25Add to TODO:Bruce Momjian
> > o Fix port/rint.c to be spec-compliant > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00808.php
2008-03-25Add to TODO:Bruce Momjian
> > * Consider sorting entries before inserting into btree index > > http://archives.postgresql.org/pgsql-general/2008-01/msg01010.php
2008-03-25Add to TODO:Bruce Momjian
> > * Improve detection of shared memory segments being used by other > FreeBSD jails > > http://archives.postgresql.org/pgsql-hackers/2008-01/msg00656.php
2008-03-25Add to TODO:Bruce Momjian
> > * 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 >
2008-03-25Add to TODO:Bruce Momjian
> > * Have resource managers report the duration of their status changes > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01468.php
2008-03-25Add to TODO:Bruce Momjian
> > * Be more aggressive about creating WAL files > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg01325.php
2008-03-25Add:Bruce Momjian
> o Prevent concurrent CREATE TABLE table1 from sometimes returning > a cryptic error message > > http://archives.postgresql.org/pgsql-bugs/2007-10/msg00169.php
2008-03-25Add to TODO:Bruce Momjian
> > * Have /contrib/dblink reuse unnamed connections > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00895.php
2008-03-25Add to TODO:Bruce Momjian
> * Remove old-style routines for manipulating tuples > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00851.php
2008-03-25Add to TODO:Bruce Momjian
> > * Create three versions of libpgport to simplify client code > > http://archives.postgresql.org/pgsql-hackers/2007-10/msg00154.php >
2008-03-25Add to TODO:Bruce Momjian
> > * Fix regular expression bug when using complex back-references > > http://archives.postgresql.org/pgsql-bugs/2007-10/msg00000.php
2008-03-24Add to TODO:Bruce Momjian
> > * 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 >
2008-03-24When a relation has been proven empty by constraint exclusion, propagate thatTom Lane
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.
2008-03-24Use new errdetail_log() mechanism to provide a less klugy way of reportingTom Lane
large numbers of dependencies on a role that couldn't be dropped. Per a comment from Alvaro.
2008-03-24Fix various infelicities that have snuck into usage of errdetail() andTom Lane
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.
2008-03-24Add to TODO:Bruce Momjian
> > * Research reducing deTOASTing in more places > > http://archives.postgresql.org/pgsql-hackers/2007-09/msg00895.php