From peter_e@gmx.net Wed Sep 29 16:28:28 1999 Received: from merganser.its.uu.se (merganser.its.uu.se [130.238.6.236]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA04185 for ; Wed, 29 Sep 1999 12:27:41 -0400 (EDT) (envelope-from peter@peter-e.yi.org) Received: from uria.its.uu.se ([130.238.7.14]:3842 "EHLO peter-e.yi.org") by merganser.its.uu.se with ESMTP id ; Wed, 29 Sep 1999 18:27:28 +0200 Received: from peter (helo=localhost) by peter-e.yi.org with local-esmtp (Exim 3.02 #2) id 11WMaj-00006D-00; Wed, 29 Sep 1999 18:28:29 +0200 Date: Wed, 29 Sep 1999 18:28:28 +0200 (CEST) From: Peter Eisentraut To: Bruce Momjian cc: Tom Lane , pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Re: TODO items In-Reply-To: <199909271519.LAA14759@candle.pha.pa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Peter Eisentraut Just my 0.02 kronor . . . On Sep 27, Bruce Momjian noted: > > * Update table SET table.value = 3 fails > > > > AFAICS, the SQL92 syntax allows only a bare as the > > target of a SET clause. Not sure it's worth expending any effort > > on this one... > > Marked now as: > > * Update table SET table.value = 3 fails(SQL standard says this is OK) In my opinion this should definitely _not_ be allowed. Let's be glad the UPDATE command is so conceptually simple (cf. SELECT). The next thing they want is ALTER TABLE foo RENAME foo.colum [ TO bar.something ??? -- moving columns between tables, why not :) ] and then CREATE TABLE foo (foo.a int, ...); and it won't stop :) > > MISC > > > > * Do autocommit so always in a transaction block(?) > > > > Huh? What is this supposed to mean? > > Some people want the SQL session to start inside a transaction, and you > have to explicity use COMMIT, at which point you are in a new > transaction that lasts until the next commit. Ingres SQL does this, and > it is a pain, I think. I have been wondering about this, too. Oracle does this as well. This is also how they taught me SQL in university, so it is probably not out of the blue. What do the standards say? Then again, while I think that client programmers won't die if they type an extra BEGIN here or there, this might be useful as a psql feature. Too many times I've seen people type DELETE FROM ; by accident. What do y'all think? (Besides the fact that this might be a pain to implement.) Peter -- Peter Eisentraut - peter_e@gmx.net http://yi.org/peter-e From maillist@candle.pha.pa.us Wed Sep 29 17:21:48 1999 Received: from candle.pha.pa.us (maillist@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA14096 for ; Wed, 29 Sep 1999 13:23:46 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id NAA03450; Wed, 29 Sep 1999 13:21:48 -0400 (EDT) From: Bruce Momjian Message-Id: <199909291721.NAA03450@candle.pha.pa.us> Subject: Re: [HACKERS] Re: TODO items In-Reply-To: from Peter Eisentraut at "Sep 29, 1999 06:28:28 pm" To: Peter Eisentraut Date: Wed, 29 Sep 1999 13:21:48 -0400 (EDT) CC: Tom Lane , pgsql-hackers@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Just my 0.02 kronor . . . > > On Sep 27, Bruce Momjian noted: > > > > * Update table SET table.value = 3 fails > > > > > > AFAICS, the SQL92 syntax allows only a bare as the > > > target of a SET clause. Not sure it's worth expending any effort > > > on this one... > > > > Marked now as: > > > > * Update table SET table.value = 3 fails(SQL standard says this is OK) > > In my opinion this should definitely _not_ be allowed. Let's be glad the > UPDATE command is so conceptually simple (cf. SELECT). The next thing they > want is ALTER TABLE foo RENAME foo.colum [ TO bar.something ??? -- moving > columns between tables, why not :) ] and then CREATE TABLE foo (foo.a int, > ...); and it won't stop :) OK, let's leave it in so people know it is not implemented. > > Some people want the SQL session to start inside a transaction, and you > > have to explicity use COMMIT, at which point you are in a new > > transaction that lasts until the next commit. Ingres SQL does this, and > > it is a pain, I think. > > I have been wondering about this, too. Oracle does this as well. This is > also how they taught me SQL in university, so it is probably not out of > the blue. What do the standards say? > > Then again, while I think that client programmers won't die if they type > an extra BEGIN here or there, this might be useful as a psql feature. Too > many times I've seen people type DELETE FROM
; by accident. No one has really been passionate about it either way. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 From pgman@candle.pha.pa.us Fri Aug 8 02:01:02 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 86621D1F419 for ; Fri, 8 Aug 2003 02:01:13 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 64326-01 for ; Thu, 7 Aug 2003 22:59:50 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 2DCC6D1C4CA for ; Thu, 7 Aug 2003 23:00:58 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h78212x26726 for pgsql-hackers@postgreSQL.org; Thu, 7 Aug 2003 22:01:02 -0400 (EDT) From: Bruce Momjian Message-Id: <200308080201.h78212x26726@candle.pha.pa.us> Subject: TODO items To: PostgreSQL-development Date: Thu, 7 Aug 2003 22:01:02 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM1060308062-11567-0_ Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/438 X-Sequence-Number: 42096 --ELM1060308062-11567-0_ Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII I am marking the completed TODO items. Are these done? * Have standalone backend read postgresql.conf * Prevent whole-row references from leaking memory, e.g. SELECT COUNT(tab.*) * Use index to restrict rows returned by multi-key index when used with non-consecutive keys or OR clauses, so fewer heap accesses * Prevent index uniqueness checks when UPDATE does not modify the column * Return proper effected tuple count from complex commands [return] o Allow SHOW of non-modifiable variables, like pg_controldata o Allow array declarations and other data types in PL/PgSQL DECLARE o Add PL/PgSQL PROCEDURES that can return multiple values o Add table function support to pltcl, plperl, plpython o Allow PL/PgSQL to support array element assignment * Allow psql to do table completion for SELECT * FROM schema_part and table completion for SELECT * FROM schema_name. o Support jdbc both 'make' and 'ant' * Make blind writes go through the file descriptor cache * Improve Subplan list handling * Precompile SQL functions to avoid overhead (Neil) * Add optional CRC checksum to heap and index pages o Add optional textual message to NOTIFY The current TODO is attached with completed items marked. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 --ELM1060308062-11567-0_ Content-Transfer-Encoding: 7bit Content-Type: text/plain Content-Disposition: inline; filename="/pgdev/TODO" TODO list for PostgreSQL ======================== Last updated: Thu Aug 7 22:00:19 EDT 2003 Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) The most recent version of this document can be viewed at the PostgreSQL web site, http://www.PostgreSQL.org. A dash (-) marks changes that will appear in the upcoming 7.4 release. Bracketed items "[]" have more detailed. Urgent ====== * Add replication of distributed databases [replication] o Automatic failover o Load balancing o Master/slave replication o Multi-master replication o Partition data across servers o Sample implementation in contrib/rserv o Queries across databases or servers (two-phase commit) o Allow replication over unreliable or non-persistent links o http://gborg.postgresql.org/project/pgreplication/projdisplay.php * Point-in-time data recovery using backup and write-ahead log * Create native Win32 port [win32] Reporting ========= * -Allow elog() to return error codes, module name, file name, line number, not just messages (Tom) * -Add error codes (Tom) * -Make error messages more consistent * Show location of syntax error in query [yacc] * -Add GUC log_statement_and_duration to print statement and >= min duration Administration ============== * Incremental backups * Remove unreferenced table files and temp tables during database vacuum or postmaster startup (Bruce) * Remove behavior of postmaster -o after making postmaster/postgres flags unique * Allow easy display of usernames in a group * Allow configuration files to be specified in a different directory * -Add start time to pg_stat_activity * Allow limits on per-db/user connections * Have standalone backend read postgresql.conf * Add group object ownership, so groups can rename/drop/grant on objects, so we can implement roles * Add the concept of dataspaces/tablespaces [tablespaces] * -Allow CIDR format to be used in pg_hba.conf * Allow logging of only data definition(DDL), or DDL and modification statements * Allow log lines to include session-level information, like database and user * Allow server log information to be output as INSERT statements Data Types ========== * -Add IPv6 capability to INET/CIDR types * Remove Money type, add money formatting for decimal type * Change factorial to return a numeric * -Change NUMERIC data type to use base 10,000 internally * Change NUMERIC to enforce the maximum precision, and increase it * Add function to return compressed length of TOAST data values (Tom) * Allow INET subnet tests using non-constants * Add transaction_timestamp(), statement_timestamp(), clock_timestamp() functionality * -Add GUC variables to control floating number output digits (Pedro Ferreira) * Have sequence dependency track use of DEFAULT sequences, seqname.nextval * Disallow changing default expression of a SERIAL column * Allow infinite dates just like infinite timestamps * Allow pg_dump to dump sequences using NO_MAXVALUE and NO_MINVALUE * Allow better handling of numeric constants, type conversion [typeconv] * Allow backend to output result sets in XML * Prevent whole-row references from leaking memory, e.g. SELECT COUNT(tab.*) * -Allow current datestyle to restrict dates; prevent month/day swapping from making invalid dates valid * -Prevent month/day swapping of ISO dates to make invalid dates valid * Have initdb set DateStyle based on locale? * -Delay resolution of array expression type so assignment coercion can be performed on empty array expressions (Joe) * ARRAYS o Allow nulls in arrays o -Allow arrays to be ORDER'ed o Support construction of array result values in expressions * BINARY DATA o Improve vacuum of large objects, like /contrib/vacuumlo o Add security checking for large objects o Make file in/out interface for TOAST columns, similar to large object interface (force out-of-line storage and no compression) o Auto-delete large objects when referencing row is deleted Multi-Language Support ====================== * Add NCHAR (as distinguished from ordinary varchar), * Allow LOCALE on a per-column basis, default to ASCII * Support multiple simultaneous character sets, per SQL92 * Improve Unicode combined character handling * Optimize locale to have minimal performance impact when not used (Peter E) * Add octet_length_server() and octet_length_client() (Thomas, Tatsuo) * Make octet_length_client the same as octet_length() (?) * Prevent mismatch of frontend/backend encodings from converting bytea data from being interpreted as encoded strings * -Remove Cyrillic recode support Views / Rules ============= * Automatically create rules on views so they are updateable, per SQL92 [view] * Add the functionality for WITH CHECK OPTION clause of CREATE VIEW * Allow NOTIFY in rules involving conditionals * Have views on temporary tables exist in the temporary namespace * Move psql backslash information into views * Allow RULE recompilation Indexes ======= * Allow CREATE INDEX zman_index ON test (date_trunc( 'day', zman ) datetime_ops) fails index can't store constant parameters * Order duplicate index entries by tid for faster heap lookups * Allow inherited tables to inherit index, UNIQUE constraint, and primary key, foreign key [inheritance] * UNIQUE INDEX on base column not honored on inserts from inherited table INSERT INTO inherit_table (unique_index_col) VALUES (dup) should fail [inheritance] * Add UNIQUE capability to non-btree indexes * Add btree index support for reltime, tinterval, regproc * Add rtree index support for line, lseg, path, point * -Certain indexes will not shrink, e.g. indexes on ever-increasing columns and indexes with many duplicate keys * Use indexes for min() and max() or convert to SELECT col FROM tab ORDER BY col DESC LIMIT 1 if appropriate index exists and WHERE clause acceptible * Allow LIKE indexing optimization for non-ASCII locales * Use index to restrict rows returned by multi-key index when used with non-consecutive keys or OR clauses, so fewer heap accesses * Be smarter about insertion of already-ordered data into btree index * Prevent index uniqueness checks when UPDATE does not modify the column * Use bitmaps to fetch heap pages in sequential order [performance] * Use bitmaps to combine existing indexes [performance] * Improve handling of index scans for NULL * Allow SELECT * FROM tab WHERE int2col = 4 to use int2col index, int8, float4, numeric/decimal too [optimizer] * Add FILLFACTOR to btree index creation * Add concurrency to GIST * Improve concurrency of hash indexes (Neil) * Allow a single index to index multiple tables (for inheritance and subtables) Commands ======== * Add BETWEEN ASYMMETRIC/SYMMETRIC (Christopher) * -Allow LIMIT/OFFSET to use expressions (Tom) * CREATE TABLE AS can not determine column lengths from expressions [atttypmod] * Allow UPDATE to handle complex aggregates [update] * Allow command blocks to ignore certain types of errors * Allow backslash handling in quoted strings to be disabled for portability * Return proper effected tuple count from complex commands [return] * Allow UPDATE, DELETE to handle table aliases for self-joins [delete] * Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT * Allow REINDEX to rebuild all indexes, remove /contrib/reindex * -Make a transaction-safe TRUNCATE (Rod) * Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY * Add schema option to createlang * Allow savepoints / nested transactions [transactions] (Bruce) * Allow UPDATE tab SET ROW (col, ...) = (...) for updating multiple columns * -Allow UPDATE to use SET col = DEFAULT * -Add config variable to prevent auto-adding missing FROM-clause tables * Allow SET CONSTRAINTS to be qualified by schema/table * -Have SELECT '13 minutes'::interval display zero seconds in ISO datestyle * Prevent COMMENT ON DATABASE from using a database name * Add GUC variable to prevent waiting on locks * ALTER o ALTER TABLE ADD COLUMN does not honor DEFAULT and non-CHECK CONSTRAINT o ALTER TABLE ADD COLUMN column DEFAULT should fill existing rows with DEFAULT value o ALTER TABLE ADD COLUMN column SERIAL doesn't create sequence because of the item above o --Add ALTER TABLE tab SET WITHOUT OIDS (Rod) o -Add ALTER SEQUENCE to modify min/max/increment/cache/cycle values o Have ALTER TABLE rename SERIAL sequences o Allow columns to be reordered using ALTER ... POSITION i col1 [,col2]; have SELECT * and INSERT honor such ordering o Allow ALTER TABLE to modify column lengths and change to binary compatible types o Add ALTER DATABASE ... OWNER TO newowner * CLUSTER o Automatically maintain clustering on a table o -Allow CLUSTER to cluster all tables (Alvaro Herrera) * COPY o Allow dump/load of CSV format o Allow COPY to report error lines and continue; optionally allow error codes to be specified; requires savepoints or can not be run in a multi-statement transaction o Allow COPY to understand \x as hex o Have COPY return number of rows loaded/unloaded * CURSOR o Allow BINARY option to SELECT, just like DECLARE o -MOVE 0 should not move to end of cursor (Bruce) o Allow UPDATE/DELETE WHERE CURRENT OF cursor using per-cursor tid stored in the backend (Gavin) o Prevent DROP of table being referenced by our own open cursor o -Allow cursors outside transactions * INSERT o Allow INSERT/UPDATE of system-generated oid value for a row o Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) o Allow INSERT/UPDATE ... RETURNING new.col or old.col; handle RULE cases (Philip) * SHOW/SET o Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM ANALYZE, and CLUSTER o Add SET SCHEMA o -Allow EXPLAIN EXECUTE to see prepared plans o Allow SHOW of non-modifiable variables, like pg_controldata * SERVER-SIDE LANGUAGES o Allow PL/PgSQL's RAISE function to take expressions o Change PL/PgSQL to use palloc() instead of malloc() o Allow Java server-side programming, http://pljava.sourceforge.net [java] o Fix problems with complex temporary table creation/destruction without using PL/PgSQL EXECUTE, needs cache prevention/invalidation o Fix PL/pgSQL RENAME to work on variables other than OLD/NEW o Improve PL/PgSQL exception handling o Allow parameters to be specified by name and type during definition o Allow function parameters to be passed by name, get_employee_salary(emp_id => 12345, tax_year => 2001) o Add PL/PgSQL packages o Allow array declarations and other data types in PL/PgSQL DECLARE o Add PL/PgSQL PROCEDURES that can return multiple values o Add table function support to pltcl, plperl, plpython o -Make PL/PgSQL %TYPE schema-aware o Allow PL/PgSQL to support array element assignment o Add PL/PHP (Joe, Jan) o Allow PL/pgSQL to name columns by ordinal position, e.g. rec.(3) o Allow PL/pgSQL EXECUTE query_var INTO record_var; Clients ======= * -Allow psql to show transaction status if backend protocol changes made * -Add schema, cast, and conversion backslash commands to psql (Christopher) * -Allow pg_dump to dump a specific schema (Neil Conway) * Allow psql to do table completion for SELECT * FROM schema_part and table completion for SELECT * FROM schema_name. * Add XML capability to pg_dump and COPY, when backend XML capability * -Allow SSL-enabled clients to turn off SSL transfers * -Modify pg_get_triggerdef() to take a boolean to pretty-print, and use that as part of pg_dump along with psql * JDBC o Comprehensive test suite. This may be available already. o JDBC-standard BLOB support o Error Codes (pending backend implementation) o Support both 'make' and 'ant' o Fix LargeObject API to handle OIDs as unsigned ints o Use cursors implicitly to avoid large results (see setCursorName()) o Add LISTEN/NOTIFY support to the JDBC driver (Barry) * ECPG o Docs o Implement set descriptor, using descriptor o Solve cardinality > 1 for input descriptors / variables o Improve error handling o Add a semantic check level, e.g. check if a table really exists o -Add SQLSTATE o fix handling of DB attributes that are arrays o Use backend prepare/execute facility for ecpg where possible o -Make casts work in variable initializations o -Implement SQLDA o Fix nested C comments o sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified o -Allow multi-threaded use of SQLCA o -Understand structure definitions outside a declare section o -Allow :var[:index] or :var[] as cvariable for an array var * Python o Allow users to register their own types with pg_ o Allow SELECT to return a dictionary of dictionaries o Allow COPY BINARY FROM Referential Integrity ===================== * Add MATCH PARTIAL referential integrity [foreign] * Add deferred trigger queue file (Jan) * Implement dirty reads or shared row locks and use them in RI triggers * Enforce referential integrity for system tables * Change foreign key constraint for array -> element to mean element in array * Allow DEFERRABLE UNIQUE constraints * Allow triggers to be disabled [trigger] * With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY * -Support statement-level triggers (Neil) * Support triggers on columns (Neil) * Have AFTER triggers execute after the appropriate SQL statement in a function, not at the end of the function Dependency Checking =================== * Flush cached query plans when their underlying catalog data changes * Use dependency information to dump data in proper order Exotic Features =============== * Add SQL99 WITH clause to SELECT (Tom, Fernando) * Add SQL99 WITH RECURSIVE to SELECT (Tom, Fernando) * Allow queries across multiple databases [crossdb] * Add pre-parsing phase that converts non-ANSI features to supported features * Allow plug-in modules to emulate features from other databases * SQL*Net listener that makes PostgreSQL appear as an Oracle database to clients * Two-phase commit to implement distributed transactions PERFORMANCE =========== Fsync ===== * Delay fsync() when other backends are about to commit too [fsync] o Determine optimal commit_delay value * Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options o Allow multiple blocks to be written to WAL with one write() Cache ===== * Shared catalog cache, reduce lseek()'s by caching table size in shared area * Add free-behind capability for large sequential scans (Bruce) * Consider use of open/fcntl(O_DIRECT) to minimize OS caching * Make blind writes go through the file descriptor cache * Cache last known per-tuple offsets to speed long tuple access * Automatically place fixed-width, NOT NULL columns first in a table * Consider using MVCC to cache count(*) queries with no WHERE clause Vacuum ====== * Improve speed with indexes (perhaps recreate index instead) [vacuum] * Reduce lock time by moving tuples with read lock, then write lock and truncate table [vacuum] * Provide automatic running of vacuum in the background in backend rather than in /contrib [vacuum] * Allow free space map to be auto-sized or warn when it is too small Locking ======= * Make locking of shared data structures more fine-grained * Add code to detect an SMP machine and handle spinlocks accordingly from distributted.net, http://www1.distributed.net/source, in client/common/cpucheck.cpp * Research use of sched_yield() for spinlock acquisition failure Startup Time ============ * Experiment with multi-threaded backend [thread] * Add connection pooling [pool] * Allow persistent backends [persistent] * Create a transaction processor to aid in persistent connections and connection pooling * Do listen() in postmaster and accept() in pre-forked backend * Have pre-forked backend pre-connect to last requested database or pass file descriptor to backend pre-forked for matching database Write-Ahead Log =============== * Have after-change WAL write()'s write only modified data to kernel * Reduce number of after-change WAL writes; they exist only to gaurd against partial page writes [wal] * Turn off after-change writes if fsync is disabled (?) * Add WAL index reliability improvement to non-btree indexes * Find proper defaults for postgresql.conf WAL entries * -Add checkpoint_min_warning postgresql.conf option to warn about checkpoints that are too frequent (Bruce) * Allow xlog directory location to be specified during initdb, perhaps using symlinks * Allow WAL information to recover corrupted pg_controldata * Find a way to reduce rotational delay when repeatedly writing last WAL page Optimizer / Executor ==================== * Improve Subplan list handling * -Allow Subplans to use efficient joins(hash, merge) with upper variable * -Add hash for evaluating GROUP BY aggregates (Tom) * -Allow merge and hash joins on expressions not just simple variables (Tom) * -Make IN/NOT IN have similar performance to EXISTS/NOT EXISTS (Tom) * Missing optimizer selectivities for date, r-tree, etc. [optimizer] * Allow ORDER BY ... LIMIT to select top values without sort or index using a sequential scan for highest/lowest values (Oleg) * -Inline simple SQL functions to avoid overhead (Tom) * Precompile SQL functions to avoid overhead (Neil) * Add utility to compute accurate random_page_cost value * Improve ability to display optimizer analysis using OPTIMIZER_DEBUG * Use CHECK constraints to improve optimizer decisions * Check GUC geqo_threshold to see if it is still accurate * Allow sorting, temp files, temp tables to use multiple work directories * Improve the planner to use CHECK constraints to prune the plan (for subtables) Miscellaneous ============= * Do async I/O for faster random read-ahead of data * -Get faster regex() code from Henry Spencer * Use mmap() rather than SYSV shared memory or to write WAL files (?) [mmap] * Improve caching of attribute offsets when NULLs exist in the row * Add a script to ask system configuration questions and tune postgresql.conf * Allow partitioning of table into multiple subtables Source Code =========== * Add use of 'const' for variables in source tree * Rename some /contrib modules from pg* to pg_* * Move some things from /contrib into main tree * Remove warnings created by -Wcast-align * Move platform-specific ps status display info from ps_status.c to ports * -Modify regression tests to prevent failures do to minor numeric rounding * -Add OpenBSD's getpeereid() call for local socket authentication * Improve access-permissions check on data directory in Cygwin (Tom) * Add documentation for perl, including mention of DBI/DBD perl location * Create improved PostgreSQL introductory documentation for the PHP manuals (Rory) * Add optional CRC checksum to heap and index pages * Change representation of whole-tuple parameters to functions * Clarify use of 'application' and 'command' tags in SGML docs * Better document ability to build only certain interfaces (Marc) * Remove or relicense modules that are not under the BSD license, if possible * Remove memory/file descriptor freeing before ereport(ERROR) (Bruce) * Acquire lock on a relation before building a relcache entry for it * Research interaction of setitimer() and sleep() used by statement_timeout * Add checks for fclose() failure * Change CVS $Id: TODO,v 1.1107 2003/08/08 02:00:20 momjian Exp $ to $PostgreSQL$ * Exit postmaster if postgresql.conf can not be opened * Rename /scripts directory because they are all C programs now * Allow the regression tests to start postmaster with -i so the tests can be run on systems that don't support unix-domain sockets * Allow creation of a libpq-only tarball * Promote debug_query_string into a server-side function current_query() * Allow the identifier length to be increased via a configure option * Wire Protocol Changes o -Show transaction status in psql o -Allow binding of query parameters, support for prepared queries o Add optional textual message to NOTIFY o -Remove hard-coded limits on user/db/password names o -Remove unused elements of startup packet (unused, tty, passlength) o -Fix COPY/fastpath protocol o Allow fastpast to pass values in portable format o -Error codes o Dynamic character set handling o Special passing of binary values in platform-neutral format (bytea?) o Add decoded type, length, precision o Compression? o -Report server version number, database encoding, client encoding o Update clients to use data types, typmod, schema.table.column names of result sets using new query protocol --------------------------------------------------------------------------- Developers who have claimed items are: -------------------------------------- * Barry is Barry Lind * Billy is Billy G. Allie * Bruce is Bruce Momjian of Software Research Assoc. * Christopher is Christopher Kings-Lynne of Family Health Network * D'Arcy is D'Arcy J.M. Cain of The Cain Gang Ltd. * Dave is Dave Cramer * Edmund is Edmund Mergl * Fernando is Fernando Nasser of Red Hat * Gavin is Gavin Sherry of Alcove Systems Engineering * Greg is Greg Sabino Mullane * Hiroshi is Hiroshi Inoue * Karel is Karel Zak * Jan is Jan Wieck of PeerDirect Corp. * Liam is Liam Stewart of Red Hat * Marc is Marc Fournier of PostgreSQL, Inc. * Mark is Mark Hollomon * Michael is Michael Meskes of Credativ * Neil is Neil Conway * Oleg is Oleg Bartunov * Peter M is Peter T Mount of Retep Software * Peter E is Peter Eisentraut * Philip is Philip Warner of Albatross Consulting Pty. Ltd. * Rod is Rod Taylor * Ross is Ross J. Reedstrom * Stephan is Stephan Szabo * Tatsuo is Tatsuo Ishii of Software Research Assoc. * Thomas is Thomas Lockhart of Jet Propulsion Labratory * Tom is Tom Lane of Red Hat * Vadim is Vadim B. Mikheev of Sector Data --ELM1060308062-11567-0_-- From josh@agliodbs.com Fri Aug 8 03:36:22 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 38F6ED1C93B for ; Fri, 8 Aug 2003 03:37:11 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 69094-08 for ; Fri, 8 Aug 2003 00:35:44 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 70C0BD1C4CA for ; Fri, 8 Aug 2003 00:36:59 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3488146; Thu, 07 Aug 2003 20:37:06 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Bruce Momjian , PostgreSQL-development Subject: Re: TODO items Date: Thu, 7 Aug 2003 20:36:22 -0700 User-Agent: KMail/1.4.3 References: <200308080201.h78212x26726@candle.pha.pa.us> In-Reply-To: <200308080201.h78212x26726@candle.pha.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200308072036.22437.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/439 X-Sequence-Number: 42097 Bruce, > o Allow array declarations and other data types in PL/PgSQL DECLARE > o Allow PL/PgSQL to support array element assignment AFAIK, these two are not done, but they are redundant. Either one requires the implementation of the other. > o Add PL/PgSQL PROCEDURES that can return multiple values Hmmm ... I know how this got on the TODO, but it's a fragment of a larger suggestion about PROCEDURES vs. FUNCTIONS. I don't think it makes much sense on its own without the other elements; maybe we should take it off until I can make a full proposal? > o Add table function support to pltcl, plperl, plpython If this was done, I would dearly love to know about it ... -- Josh Berkus Aglio Database Solutions San Francisco From mail@joeconway.com Fri Aug 8 04:00:28 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4D187D1C4CA for ; Fri, 8 Aug 2003 04:04:47 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 69399-08 for ; Fri, 8 Aug 2003 01:03:20 -0300 (ADT) Received: from joeconway.com (66-146-172-86.skyriver.net [66.146.172.86]) by svr1.postgresql.org (Postfix) with ESMTP id 7E4A2D1C513 for ; Fri, 8 Aug 2003 01:04:34 -0300 (ADT) Received: from [192.168.5.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 4.0.6) with ESMTP-TLS id 26124; Thu, 07 Aug 2003 20:25:08 -0700 Message-ID: <3F33205C.6040308@joeconway.com> Date: Thu, 07 Aug 2003 21:00:28 -0700 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josh Berkus Cc: Bruce Momjian , PostgreSQL-development Subject: Re: TODO items References: <200308080201.h78212x26726@candle.pha.pa.us> <200308072036.22437.josh@agliodbs.com> In-Reply-To: <200308072036.22437.josh@agliodbs.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/442 X-Sequence-Number: 42100 Josh Berkus wrote: >> o Allow array declarations and other data types in PL/PgSQL DECLARE >> o Allow PL/PgSQL to support array element assignment > > AFAIK, these two are not done, but they are redundant. Either one requires > the implementation of the other. They are done (at least the array declarations and array element assignment part): create or replace function test() returns integer[] as ' declare v_ret integer[] := ''{}''; begin v_ret[1] := 1; v_ret[2] := 2; return v_ret; end; ' language plpgsql; CREATE FUNCTION regression=# select test(); test ------- {1,2} (1 row) >> o Add PL/PgSQL PROCEDURES that can return multiple values > > Hmmm ... I know how this got on the TODO, but it's a fragment of a larger > suggestion about PROCEDURES vs. FUNCTIONS. I don't think it makes much > sense on its own without the other elements; maybe we should take it off > until I can make a full proposal? Is this somehow different from table functions (SRFs)? >> o Add table function support to pltcl, plperl, plpython > > If this was done, I would dearly love to know about it ... > Pretty much sure this has not been done. I'll be happy to work with someone if they want to pick this up, but I don't use them enough to feel comfortable doing it myself. Joe From mail@joeconway.com Fri Aug 8 04:24:29 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 11A22D1C4E6 for ; Fri, 8 Aug 2003 04:28:46 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 76416-06 for ; Fri, 8 Aug 2003 01:27:19 -0300 (ADT) Received: from joeconway.com (66-146-172-86.skyriver.net [66.146.172.86]) by svr1.postgresql.org (Postfix) with ESMTP id C74D4D1C4CA for ; Fri, 8 Aug 2003 01:28:34 -0300 (ADT) Received: from [192.168.5.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 4.0.6) with ESMTP-TLS id 26131; Thu, 07 Aug 2003 20:49:08 -0700 Message-ID: <3F3325FD.6060007@joeconway.com> Date: Thu, 07 Aug 2003 21:24:29 -0700 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruce Momjian Cc: PostgreSQL-development Subject: Re: TODO items References: <200308080201.h78212x26726@candle.pha.pa.us> In-Reply-To: <200308080201.h78212x26726@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/443 X-Sequence-Number: 42101 Bruce Momjian wrote: > I am marking the completed TODO items. Are these done? > Can we mark this one complete? * Allow easy display of usernames in a group regression=# SELECT g.grosysid, g.groname, s.usesysid, s.usename FROM pg_shadow s, pg_group g WHERE s.usesysid = any (g.grolist); grosysid | groname | usesysid | usename ----------+---------+----------+--------- 100 | g1 | 100 | user1 101 | g2 | 100 | user1 100 | g1 | 101 | user2 101 | g2 | 101 | user2 101 | g2 | 102 | user3 (5 rows) This one isn't done: * -Delay resolution of array expression type so assignment coercion can be performed on empty array expressions (Joe) This one I don't understand: o Support construction of array result values in expressions I thought Peter did something with this one: * Allow LIKE indexing optimization for non-ASCII locales Joe From josh@agliodbs.com Fri Aug 8 04:35:01 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9083CD1C4E6 for ; Fri, 8 Aug 2003 04:35:33 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 69927-08 for ; Fri, 8 Aug 2003 01:34:07 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 8A88FD1C4CA for ; Fri, 8 Aug 2003 01:35:22 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3488238; Thu, 07 Aug 2003 21:35:45 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Joe Conway Subject: Re: TODO items Date: Thu, 7 Aug 2003 21:35:01 -0700 User-Agent: KMail/1.4.3 Cc: Bruce Momjian , PostgreSQL-development References: <200308080201.h78212x26726@candle.pha.pa.us> <200308072036.22437.josh@agliodbs.com> <3F33205C.6040308@joeconway.com> In-Reply-To: <3F33205C.6040308@joeconway.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200308072135.01205.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/444 X-Sequence-Number: 42102 Joe, > They are done (at least the array declarations and array element > assignment part): Way cool! How'd I miss that one? Time to test .... > >> o Add PL/PgSQL PROCEDURES that can return multiple values > > > > Hmmm ... I know how this got on the TODO, but it's a fragment of a larger > > suggestion about PROCEDURES vs. FUNCTIONS. I don't think it makes much > > sense on its own without the other elements; maybe we should take it off > > until I can make a full proposal? > > Is this somehow different from table functions (SRFs)? Yes. Reference T-SQL's OUTPUT parameters. Mind you, with the implementation of SRFs, it's not as necessary as it once was. > Pretty much sure this has not been done. I'll be happy to work with > someone if they want to pick this up, but I don't use them enough to > feel comfortable doing it myself. I'd be happy to test PL/Perl. I won't be any help with the others ... -- Josh Berkus Aglio Database Solutions San Francisco From tgl@sss.pgh.pa.us Fri Aug 8 13:56:34 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 44428D1C965 for ; Fri, 8 Aug 2003 13:56:55 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 33496-07 for ; Fri, 8 Aug 2003 10:55:31 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 4606DD1C93B for ; Fri, 8 Aug 2003 10:56:44 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h78DuZSa020636; Fri, 8 Aug 2003 09:56:35 -0400 (EDT) To: Bruce Momjian Cc: PostgreSQL-development Subject: Re: TODO items In-reply-to: <200308080201.h78212x26726@candle.pha.pa.us> References: <200308080201.h78212x26726@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Thu, 07 Aug 2003 22:01:02 -0400" Date: Fri, 08 Aug 2003 09:56:34 -0400 Message-ID: <20635.1060350994@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/467 X-Sequence-Number: 42125 Bruce Momjian writes: > I am marking the completed TODO items. Are these done? > * Have standalone backend read postgresql.conf [looks] Nope. No ProcessConfigFile() call in postgres.c. > * Prevent whole-row references from leaking memory, e.g. SELECT > COUNT(tab.*) Nope. > * Use index to restrict rows returned by multi-key index when used with > non-consecutive keys or OR clauses, so fewer heap accesses Not sure what this means. > * Prevent index uniqueness checks when UPDATE does not modify the column Not done. > * Return proper effected tuple count from complex commands [return] I looked at that TODO.detail file, and it all seems to be ancient history. Didn't we resolve those issues to peoples' satisfaction in 7.3? > o Allow SHOW of non-modifiable variables, like pg_controldata I put in read-only variables for the things that seemed most interesting (LC_COLLATE for example), but the coverage isn't complete. > o Allow array declarations and other data types in PL/PgSQL DECLARE AFAIK this is pretty much fixed. > o Add PL/PgSQL PROCEDURES that can return multiple values Not done (unless this is referring to RETURN NEXT, but I think it's talking about multiple output parameters). > o Add table function support to pltcl, plperl, plpython Not done. > o Allow PL/PgSQL to support array element assignment Done. > * Make blind writes go through the file descriptor cache Not done. > * Improve Subplan list handling Dunno what this is referring to. > * Precompile SQL functions to avoid overhead (Neil) Not done. > * Add optional CRC checksum to heap and index pages Not done. > o Add optional textual message to NOTIFY Not done, but there is room in the FE/BE protocol now for something like this. regards, tom lane From tgl@sss.pgh.pa.us Fri Aug 8 14:11:07 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 360ADD1C9AB for ; Fri, 8 Aug 2003 14:11:30 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 36468-05 for ; Fri, 8 Aug 2003 11:10:07 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 0FC98D1C983 for ; Fri, 8 Aug 2003 11:11:19 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h78EB8Sa021945; Fri, 8 Aug 2003 10:11:08 -0400 (EDT) To: Joe Conway Cc: Bruce Momjian , PostgreSQL-development Subject: Re: TODO items In-reply-to: <3F3325FD.6060007@joeconway.com> References: <200308080201.h78212x26726@candle.pha.pa.us> <3F3325FD.6060007@joeconway.com> Comments: In-reply-to Joe Conway message dated "Thu, 07 Aug 2003 21:24:29 -0700" Date: Fri, 08 Aug 2003 10:11:07 -0400 Message-ID: <21944.1060351867@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/469 X-Sequence-Number: 42127 Joe Conway writes: > This one I don't understand: > o Support construction of array result values in expressions Not sure why you don't understand it, when you did it ;-). It's asking for the ARRAY[] syntax. Bruce, that one should be marked done. > I thought Peter did something with this one: > * Allow LIKE indexing optimization for non-ASCII locales Yeah, he did. regards, tom lane From pgman@candle.pha.pa.us Fri Aug 8 16:33:52 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4C203D1C9B3 for ; Fri, 8 Aug 2003 16:34:11 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 49029-05 for ; Fri, 8 Aug 2003 13:32:43 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 4F9A9D1C937 for ; Fri, 8 Aug 2003 13:33:59 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h78GXqW27012; Fri, 8 Aug 2003 12:33:52 -0400 (EDT) From: Bruce Momjian Message-Id: <200308081633.h78GXqW27012@candle.pha.pa.us> Subject: Re: TODO items In-Reply-To: <200308072036.22437.josh@agliodbs.com> To: Josh Berkus Date: Fri, 8 Aug 2003 12:33:52 -0400 (EDT) Cc: PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/485 X-Sequence-Number: 42143 Josh Berkus wrote: > Bruce, > > > o Allow array declarations and other data types in PL/PgSQL DECLARE > > o Allow PL/PgSQL to support array element assignment > > AFAIK, these two are not done, but they are redundant. Either one requires > the implementation of the other. OK. > > o Add PL/PgSQL PROCEDURES that can return multiple values > > Hmmm ... I know how this got on the TODO, but it's a fragment of a larger > suggestion about PROCEDURES vs. FUNCTIONS. I don't think it makes much > sense on its own without the other elements; maybe we should take it off > until I can make a full proposal? Removed. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 From pgman@candle.pha.pa.us Fri Aug 8 16:35:13 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 8C12ED1C91F for ; Fri, 8 Aug 2003 16:35:34 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 51040-03 for ; Fri, 8 Aug 2003 13:34:06 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id E6EA1D1C4BF for ; Fri, 8 Aug 2003 13:35:22 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h78GZDd27161; Fri, 8 Aug 2003 12:35:13 -0400 (EDT) From: Bruce Momjian Message-Id: <200308081635.h78GZDd27161@candle.pha.pa.us> Subject: Re: TODO items In-Reply-To: <3F33205C.6040308@joeconway.com> To: Joe Conway Date: Fri, 8 Aug 2003 12:35:13 -0400 (EDT) Cc: Josh Berkus , PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/484 X-Sequence-Number: 42142 Joe Conway wrote: > Josh Berkus wrote: > >> o Allow array declarations and other data types in PL/PgSQL DECLARE > >> o Allow PL/PgSQL to support array element assignment > > > > AFAIK, these two are not done, but they are redundant. Either one requires > > the implementation of the other. > > They are done (at least the array declarations and array element > assignment part): > > create or replace function test() returns integer[] as ' > declare > v_ret integer[] := ''{}''; > begin > v_ret[1] := 1; > v_ret[2] := 2; > return v_ret; > end; > ' language plpgsql; > CREATE FUNCTION > regression=# select test(); > test > ------- > {1,2} > (1 row) > OK, marked as done. > >> o Add PL/PgSQL PROCEDURES that can return multiple values > > > > Hmmm ... I know how this got on the TODO, but it's a fragment of a larger > > suggestion about PROCEDURES vs. FUNCTIONS. I don't think it makes much > > sense on its own without the other elements; maybe we should take it off > > until I can make a full proposal? > > Is this somehow different from table functions (SRFs)? Yes, I am unsure what it is. Removed pending later proposal. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 From pgman@candle.pha.pa.us Fri Aug 8 16:53:52 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id E75BDD1C984 for ; Fri, 8 Aug 2003 16:54:31 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 52636-06 for ; Fri, 8 Aug 2003 13:53:04 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id BDB22D1C937 for ; Fri, 8 Aug 2003 13:54:19 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h78Grqb28807; Fri, 8 Aug 2003 12:53:52 -0400 (EDT) From: Bruce Momjian Message-Id: <200308081653.h78Grqb28807@candle.pha.pa.us> Subject: Re: TODO items In-Reply-To: <3F3325FD.6060007@joeconway.com> To: Joe Conway Date: Fri, 8 Aug 2003 12:53:52 -0400 (EDT) Cc: PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/490 X-Sequence-Number: 42148 Joe Conway wrote: > Bruce Momjian wrote: > > I am marking the completed TODO items. Are these done? > > > > Can we mark this one complete? > * Allow easy display of usernames in a group > regression=# SELECT g.grosysid, g.groname, s.usesysid, s.usename FROM > pg_shadow s, pg_group g WHERE s.usesysid = any (g.grolist); > grosysid | groname | usesysid | usename > ----------+---------+----------+--------- > 100 | g1 | 100 | user1 > 101 | g2 | 100 | user1 > 100 | g1 | 101 | user2 > 101 | g2 | 101 | user2 > 101 | g2 | 102 | user3 > (5 rows) OK, let me mark it as done, and add to the psql section: * Allow psql \du to show groups, and add \dg for groups > This one isn't done: > * -Delay resolution of array expression type so assignment coercion > can be performed on empty array expressions (Joe) OK. > This one I don't understand: > o Support construction of array result values in expressions I don't either. Anyone? > I thought Peter did something with this one: > * Allow LIKE indexing optimization for non-ASCII locales He added a special LIKE operator type, rather than allowing our existing indexes to use LIKE, so I would say it is partially done. I updated it to: * -Allow LIKE indexing optimization for non-ASCII locales using special index and marked it as done. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 From pgman@candle.pha.pa.us Fri Aug 8 16:55:02 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 1EEE5D1C9B8 for ; Fri, 8 Aug 2003 16:57:38 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 54004-03 for ; Fri, 8 Aug 2003 13:56:10 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 83B5ED1C983 for ; Fri, 8 Aug 2003 13:57:23 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h78Gt2028909; Fri, 8 Aug 2003 12:55:02 -0400 (EDT) From: Bruce Momjian Message-Id: <200308081655.h78Gt2028909@candle.pha.pa.us> Subject: Re: TODO items In-Reply-To: <200308072135.01205.josh@agliodbs.com> To: Josh Berkus Date: Fri, 8 Aug 2003 12:55:02 -0400 (EDT) Cc: Joe Conway , PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/489 X-Sequence-Number: 42147 Josh Berkus wrote: > Joe, > > > They are done (at least the array declarations and array element > > assignment part): > > Way cool! How'd I miss that one? > > Time to test .... > > > >> o Add PL/PgSQL PROCEDURES that can return multiple values > > > > > > Hmmm ... I know how this got on the TODO, but it's a fragment of a larger > > > suggestion about PROCEDURES vs. FUNCTIONS. I don't think it makes much > > > sense on its own without the other elements; maybe we should take it off > > > until I can make a full proposal? > > > > Is this somehow different from table functions (SRFs)? > > Yes. Reference T-SQL's OUTPUT parameters. > > Mind you, with the implementation of SRFs, it's not as necessary as it once > was. Do you have TODO to add for this? I removed the original one because, as worded, it was complete. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 From mail@joeconway.com Fri Aug 8 17:01:46 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id A0458D1C922 for ; Fri, 8 Aug 2003 17:06:07 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 52418-04 for ; Fri, 8 Aug 2003 14:04:39 -0300 (ADT) Received: from joeconway.com (66-146-172-86.skyriver.net [66.146.172.86]) by svr1.postgresql.org (Postfix) with ESMTP id 359BCD1C91F for ; Fri, 8 Aug 2003 14:05:56 -0300 (ADT) Received: from [206.19.64.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 4.0.6) with ESMTP-TLS id 26569; Fri, 08 Aug 2003 09:26:22 -0700 Message-ID: <3F33D77A.6060706@joeconway.com> Date: Fri, 08 Aug 2003 10:01:46 -0700 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruce Momjian Cc: Josh Berkus , PostgreSQL-development Subject: Re: TODO items References: <200308081655.h78Gt2028909@candle.pha.pa.us> In-Reply-To: <200308081655.h78Gt2028909@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/487 X-Sequence-Number: 42145 Bruce Momjian wrote: >>>>> o Add PL/PgSQL PROCEDURES that can return multiple values >>>> > > Do you have TODO to add for this? I removed the original one because, > as worded, it was complete. > Actually, now that I look at it again, it is referring to procedures, not functions. Maybe just make it: o Add capability to create and call PROCEDURES Joe From pgman@candle.pha.pa.us Fri Aug 8 17:09:38 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9FD48D1C4BF for ; Fri, 8 Aug 2003 17:10:20 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 49652-08 for ; Fri, 8 Aug 2003 14:08:52 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 7916ED1C932 for ; Fri, 8 Aug 2003 14:10:06 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h78H9cO00606; Fri, 8 Aug 2003 13:09:38 -0400 (EDT) From: Bruce Momjian Message-Id: <200308081709.h78H9cO00606@candle.pha.pa.us> Subject: Re: TODO items In-Reply-To: <20635.1060350994@sss.pgh.pa.us> To: Tom Lane Date: Fri, 8 Aug 2003 13:09:38 -0400 (EDT) Cc: PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/497 X-Sequence-Number: 42155 Tom Lane wrote: > Bruce Momjian writes: > > I am marking the completed TODO items. Are these done? > > > * Have standalone backend read postgresql.conf > > [looks] Nope. No ProcessConfigFile() call in postgres.c. OK. > > > * Prevent whole-row references from leaking memory, e.g. SELECT > > COUNT(tab.*) > > Nope. OK, I wasn't sure because you had done per-tuple memory contexts. > > * Use index to restrict rows returned by multi-key index when used with > > non-consecutive keys or OR clauses, so fewer heap accesses > > Not sure what this means. This is a Vadim idea. The idea was that if you had a multi-key index on col1,col2,col3, and you wanted to do a lookup on col1,col3, you could still use the index, and just run through all the matching col1 values looking for a matching col3 in the index, rather than going to the heap and looking for a col3 match? Is this item worth keeping? > > > * Prevent index uniqueness checks when UPDATE does not modify the column > > Not done. OK. > > * Return proper effected tuple count from complex commands [return] > > I looked at that TODO.detail file, and it all seems to be ancient > history. Didn't we resolve those issues to peoples' satisfaction in 7.3? I think so. I think MOVE was our last one. > > o Allow SHOW of non-modifiable variables, like pg_controldata > > I put in read-only variables for the things that seemed most interesting > (LC_COLLATE for example), but the coverage isn't complete. I modified the item to say "some" and marked it as done: o -Allow SHOW of some non-modifiable variables, like pg_controldata Anyone want it kept? > > o Allow array declarations and other data types in PL/PgSQL DECLARE > > AFAIK this is pretty much fixed. OK. Already reported by Joe. > > > o Add PL/PgSQL PROCEDURES that can return multiple values > > Not done (unless this is referring to RETURN NEXT, but I think it's > talking about multiple output parameters). I am asking Josh for a new item with clearer wording. Once we finish some items, the wording often needs adjusting. > > o Add table function support to pltcl, plperl, plpython > > Not done. OK. > > o Allow PL/PgSQL to support array element assignment > > Done. OK. > > * Make blind writes go through the file descriptor cache > > Not done. OK. > > > * Improve Subplan list handling > > Dunno what this is referring to. I assume it is related to the subquery stuff you did. I have marked it as done. > > * Precompile SQL functions to avoid overhead (Neil) > > Not done. OK. > > * Add optional CRC checksum to heap and index pages > > Not done. OK. > > o Add optional textual message to NOTIFY > > Not done, but there is room in the FE/BE protocol now for something like > this. OK. Thanks. TODO updated. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 From pgman@candle.pha.pa.us Fri Aug 8 17:12:24 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id A24D0D1C983 for ; Fri, 8 Aug 2003 17:12:51 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 50420-10 for ; Fri, 8 Aug 2003 14:11:24 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 4D1F4D1C922 for ; Fri, 8 Aug 2003 14:12:38 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h78HCOZ00831; Fri, 8 Aug 2003 13:12:24 -0400 (EDT) From: Bruce Momjian Message-Id: <200308081712.h78HCOZ00831@candle.pha.pa.us> Subject: Re: TODO items In-Reply-To: <21944.1060351867@sss.pgh.pa.us> To: Tom Lane Date: Fri, 8 Aug 2003 13:12:24 -0400 (EDT) Cc: Joe Conway , PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/496 X-Sequence-Number: 42154 Tom Lane wrote: > Joe Conway writes: > > This one I don't understand: > > o Support construction of array result values in expressions > > Not sure why you don't understand it, when you did it ;-). It's asking > for the ARRAY[] syntax. Bruce, that one should be marked done. Updated as done. > > I thought Peter did something with this one: > > * Allow LIKE indexing optimization for non-ASCII locales > > Yeah, he did. Yes, wording updated and marked as done. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 From pgman@candle.pha.pa.us Fri Aug 8 17:13:06 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id E9986D1C983 for ; Fri, 8 Aug 2003 17:13:36 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 51702-07 for ; Fri, 8 Aug 2003 14:12:09 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id DD01AD1C4BF for ; Fri, 8 Aug 2003 14:13:18 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h78HD6h00928; Fri, 8 Aug 2003 13:13:06 -0400 (EDT) From: Bruce Momjian Message-Id: <200308081713.h78HD6h00928@candle.pha.pa.us> Subject: Re: TODO items In-Reply-To: <3F33D77A.6060706@joeconway.com> To: Joe Conway Date: Fri, 8 Aug 2003 13:13:06 -0400 (EDT) Cc: Josh Berkus , PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/495 X-Sequence-Number: 42153 OK, TODO updated. --------------------------------------------------------------------------- Joe Conway wrote: > Bruce Momjian wrote: > >>>>> o Add PL/PgSQL PROCEDURES that can return multiple values > >>>> > > > > Do you have TODO to add for this? I removed the original one because, > > as worded, it was complete. > > > > Actually, now that I look at it again, it is referring to procedures, > not functions. Maybe just make it: > > o Add capability to create and call PROCEDURES > > Joe > > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 From josh@agliodbs.com Fri Aug 8 17:22:22 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id DB51ED1C922 for ; Fri, 8 Aug 2003 17:24:17 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 61289-03 for ; Fri, 8 Aug 2003 14:22:50 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id DDC27D1C4DB for ; Fri, 8 Aug 2003 14:24:06 -0300 (ADT) Received: from [66.219.92.2] (HELO temoku) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3489619; Fri, 08 Aug 2003 10:24:00 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Bruce Momjian , Joe Conway Subject: Re: TODO items Date: Fri, 8 Aug 2003 10:22:22 -0700 User-Agent: KMail/1.4.3 Cc: PostgreSQL-development References: <200308081713.h78HD6h00928@candle.pha.pa.us> In-Reply-To: <200308081713.h78HD6h00928@candle.pha.pa.us> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200308081022.22741.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/493 X-Sequence-Number: 42151 Bruce, > > Actually, now that I look at it again, it is referring to procedures,= =20 > > not functions. Maybe just make it: > >=20 > > o Add capability to create and call PROCEDURES OK. I need to put a full proposal behind this once 7.4 is in the can.=20= =20 However, this is largely academic until we get someone who really wants to= =20 take ownership of PL/pgSQL and has the coding skills (I have the former but= =20 not the latter).=20=20 --=20 -Josh Berkus Aglio Database Solutions San Francisco From tgl@sss.pgh.pa.us Fri Aug 8 17:26:17 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9EB3BD1C983 for ; Fri, 8 Aug 2003 17:26:54 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 53665-09 for ; Fri, 8 Aug 2003 14:25:26 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 6925DD1C922 for ; Fri, 8 Aug 2003 14:26:43 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h78HQISa028342; Fri, 8 Aug 2003 13:26:18 -0400 (EDT) To: Bruce Momjian Cc: PostgreSQL-development Subject: Re: TODO items In-reply-to: <200308081709.h78H9cO00606@candle.pha.pa.us> References: <200308081709.h78H9cO00606@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Fri, 08 Aug 2003 13:09:38 -0400" Date: Fri, 08 Aug 2003 13:26:17 -0400 Message-ID: <28341.1060363577@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/492 X-Sequence-Number: 42150 Bruce Momjian writes: >>> * Use index to restrict rows returned by multi-key index when used with >>> non-consecutive keys or OR clauses, so fewer heap accesses >> >> Not sure what this means. > This is a Vadim idea. The idea was that if you had a multi-key index on > col1,col2,col3, and you wanted to do a lookup on col1,col3, you could > still use the index, and just run through all the matching col1 values > looking for a matching col3 in the index, rather than going to the heap > and looking for a col3 match? Is this item worth keeping? Hmm. Maybe. Might as well leave it there awhile longer. regards, tom lane From mail@joeconway.com Fri Aug 8 17:38:03 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 20DBED1C9B3 for ; Fri, 8 Aug 2003 17:42:27 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 61532-08 for ; Fri, 8 Aug 2003 14:40:59 -0300 (ADT) Received: from joeconway.com (66-146-172-86.skyriver.net [66.146.172.86]) by svr1.postgresql.org (Postfix) with ESMTP id B38DDD1C984 for ; Fri, 8 Aug 2003 14:42:15 -0300 (ADT) Received: from [206.19.64.3] (account jconway HELO joeconway.com) by joeconway.com (CommuniGate Pro SMTP 4.0.6) with ESMTP-TLS id 26601; Fri, 08 Aug 2003 10:02:41 -0700 Message-ID: <3F33DFFB.7010909@joeconway.com> Date: Fri, 08 Aug 2003 10:38:03 -0700 From: Joe Conway User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: josh@agliodbs.com Cc: Bruce Momjian , PostgreSQL-development Subject: Re: TODO items References: <200308081713.h78HD6h00928@candle.pha.pa.us> <200308081022.22741.josh@agliodbs.com> In-Reply-To: <200308081022.22741.josh@agliodbs.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/502 X-Sequence-Number: 42160 Josh Berkus wrote: >>>Actually, now that I look at it again, it is referring to procedures, >>>not functions. Maybe just make it: >>> >>>o Add capability to create and call PROCEDURES > > OK. I need to put a full proposal behind this once 7.4 is in the can. > However, this is largely academic until we get someone who really wants to > take ownership of PL/pgSQL and has the coding skills (I have the former but > not the latter). > This isn't isolated to just PL/pgSQL, just like the ability to create and call functions isn't. Support for PROCEDUREs in the backend is a prerequisite to being able to use PL/pgSQL to create procedures. It is necessary but not sufficient. Similarly, if we want to support IN/OUT or named parameters, it isn't a PL/pgSQL issue per se, it is a general one. Joe From hannu@tm.ee Tue Aug 12 22:25:17 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 829A1D1B539 for ; Tue, 12 Aug 2003 22:32:35 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 25660-03 for ; Tue, 12 Aug 2003 19:31:02 -0300 (ADT) Received: from fuji.krosing.net (unknown [194.204.44.104]) by svr1.postgresql.org (Postfix) with ESMTP id 9060BD1C4B8 for ; Tue, 12 Aug 2003 19:32:22 -0300 (ADT) Received: from fuji.krosing.net (localhost.localdomain [127.0.0.1]) by fuji.krosing.net (8.12.8/8.12.8) with ESMTP id h7CMPKB9013788; Wed, 13 Aug 2003 01:25:20 +0300 Received: (from hannu@localhost) by fuji.krosing.net (8.12.8/8.12.8/Submit) id h7CMPHQk013786; Wed, 13 Aug 2003 01:25:17 +0300 X-Authentication-Warning: fuji.krosing.net: hannu set sender to hannu@tm.ee using -f Subject: Re: TODO items From: Hannu Krosing To: Tom Lane Cc: Bruce Momjian , PostgreSQL-development In-Reply-To: <20635.1060350994@sss.pgh.pa.us> References: <200308080201.h78212x26726@candle.pha.pa.us> <20635.1060350994@sss.pgh.pa.us> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1060727117.2318.43.camel@fuji.krosing.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Wed, 13 Aug 2003 01:25:17 +0300 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/730 X-Sequence-Number: 42388 Tom Lane kirjutas R, 08.08.2003 kell 16:56: > Bruce Momjian writes: > > o Add optional textual message to NOTIFY > > Not done, but there is room in the FE/BE protocol now for something like > this. Were there any other changes to NOTIFY - there was talk about making NOTIFY use some other structure instead of ordinary PG tables in backend. ------ Hannu From pgman@candle.pha.pa.us Wed Aug 13 00:53:17 2003 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id A9414D1C4BA for ; Wed, 13 Aug 2003 00:53:44 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 38953-03 for ; Tue, 12 Aug 2003 21:52:13 -0300 (ADT) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id 4DD21D1C4B8 for ; Tue, 12 Aug 2003 21:53:32 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id h7D0rHj10305; Tue, 12 Aug 2003 20:53:17 -0400 (EDT) From: Bruce Momjian Message-Id: <200308130053.h7D0rHj10305@candle.pha.pa.us> Subject: Re: TODO items In-Reply-To: <1060727117.2318.43.camel@fuji.krosing.net> To: Hannu Krosing Date: Tue, 12 Aug 2003 20:53:17 -0400 (EDT) Cc: Tom Lane , PostgreSQL-development X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/736 X-Sequence-Number: 42394 No, I don't think any of that was done, particularly because there was no discussion of the implemention. --------------------------------------------------------------------------- Hannu Krosing wrote: > Tom Lane kirjutas R, 08.08.2003 kell 16:56: > > Bruce Momjian writes: > > > o Add optional textual message to NOTIFY > > > > Not done, but there is room in the FE/BE protocol now for something like > > this. > > Were there any other changes to NOTIFY - there was talk about making > NOTIFY use some other structure instead of ordinary PG tables in > backend. > > ------ > Hannu > -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 From gsstark@mit.edu Tue Aug 3 05:06:40 2004 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1DC5CD1B195 for ; Tue, 3 Aug 2004 02:06:54 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 84123-10 for ; Tue, 3 Aug 2004 05:06:45 +0000 (GMT) Received: from stark.xeocode.com (gsstark.mtl.istop.com [66.11.160.162]) by svr1.postgresql.org (Postfix) with ESMTP id D2598D1B182 for ; Tue, 3 Aug 2004 02:06:43 -0300 (ADT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1BrrVY-0004yQ-00; Tue, 03 Aug 2004 01:06:40 -0400 To: pgsql-hackers@postgresql.org Subject: TODO Items From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 03 Aug 2004 01:06:40 -0400 In-Reply-To: <200408030208.i73280J26911@candle.pha.pa.us> Message-ID: <874qnkolnj.fsf@stark.xeocode.com> Lines: 28 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/94 X-Sequence-Number: 57066 Bruce Momjian writes: > TODO item? On that note several prior conversations I had here ended with WIBNI conclusions that really ought to be TODO items, in my humble opinion. Two come to mind off the top of my head resulting in: . "SELECT * FROM x JOIN y USING (b) WHERE a=?" could use an index on y(a,b) since for a constant value of "a" the index traversal would be effectively equivalent just be "b". This could result in an efficient merge join avoiding an unnecessary sort. . The semantics for row-value expressions is wrong. (a,b) < (x,y) should be true if a behaviour (ie btree indexable behaviour). . Allow multi-column indexes to be used to optimize row-value expressions. Ie, allow a btree index on a,b to be used to execute an expression like (a,b) < (x,y). -- greg From pgman@candle.pha.pa.us Wed Aug 4 02:15:39 2004 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A8707D1B1AA for ; Tue, 3 Aug 2004 23:15:37 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 69013-04 for ; Wed, 4 Aug 2004 02:15:37 +0000 (GMT) Received: from candle.pha.pa.us (candle.pha.pa.us [207.106.42.251]) by svr1.postgresql.org (Postfix) with ESMTP id BC4EAD1B1C9 for ; Tue, 3 Aug 2004 23:15:32 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id i742Fdt08424; Tue, 3 Aug 2004 22:15:39 -0400 (EDT) From: Bruce Momjian Message-Id: <200408040215.i742Fdt08424@candle.pha.pa.us> Subject: Re: TODO Items In-Reply-To: <874qnkolnj.fsf@stark.xeocode.com> To: Greg Stark Date: Tue, 3 Aug 2004 22:15:39 -0400 (EDT) Cc: pgsql-hackers@postgresql.org X-Mailer: ELM [version 2.4ME+ PL108 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/148 X-Sequence-Number: 57120 Greg Stark wrote: > > Bruce Momjian writes: > > > TODO item? > > On that note several prior conversations I had here ended with WIBNI > conclusions that really ought to be TODO items, in my humble opinion. Two come > to mind off the top of my head resulting in: > > . "SELECT * FROM x JOIN y USING (b) WHERE a=?" could use an index on y(a,b) > since for a constant value of "a" the index traversal would be effectively > equivalent just be "b". This could result in an efficient merge join > avoiding an unnecessary sort. > > . The semantics for row-value expressions is wrong. (a,b) < (x,y) should be > true if a > . Fix row-value expression handling to not depend on the operator names and > instead use btree access method strategy values instead, allowing row-value > expressions on other operators with <,=,> behaviour (ie btree indexable > behaviour). > > . Allow multi-column indexes to be used to optimize row-value expressions. Ie, > allow a btree index on a,b to be used to execute an expression like (a,b) < > (x,y). I have not heard of any of those so I have not been actively excluding them from the TODO list. However, I need someone with optimizer experience to make a recommendation. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 From gsstark@mit.edu Wed Aug 4 03:25:47 2004 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id ABE70D1B344 for ; Wed, 4 Aug 2004 03:04:31 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 23077-03 for ; Wed, 4 Aug 2004 06:04:10 +0000 (GMT) Received: from www.postgresql.com (www.postgresql.com [200.46.204.209]) by svr1.postgresql.org (Postfix) with ESMTP id 9D624D1B34A for ; Wed, 4 Aug 2004 03:02:44 -0300 (ADT) Received: from stark.xeocode.com (gsstark.mtl.istop.com [66.11.160.162]) by www.postgresql.com (Postfix) with ESMTP id 39C01CF4D3D for ; Wed, 4 Aug 2004 00:33:58 -0300 (ADT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1BsCPU-00088g-00; Tue, 03 Aug 2004 23:25:48 -0400 To: Bruce Momjian Cc: Greg Stark , pgsql-hackers@postgresql.org Subject: Re: TODO Items References: <200408040215.i742Fdt08424@candle.pha.pa.us> In-Reply-To: <200408040215.i742Fdt08424@candle.pha.pa.us> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 03 Aug 2004 23:25:47 -0400 Message-ID: <87brhrmvno.fsf@stark.xeocode.com> Lines: 22 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/161 X-Sequence-Number: 57133 Bruce Momjian writes: > > . Allow multi-column indexes to be used to optimize row-value expressions. Ie, > > allow a btree index on a,b to be used to execute an expression like (a,b) < > > (x,y). > > I have not heard of any of those so I have not been actively excluding > them from the TODO list. However, I need someone with optimizer > experience to make a recommendation. Well the row-value expression stuff comes out of a discussion just this week. You could check messages on pgsql-performance with the subject "[PERFORM] best way to fetch next/prev record based on index". In particular Tom's messages from Wednesday the 28th might be relevant. The optimization in the first one came up in a conversation that was quite a bit older. I don't have that thread saved. It seems like an obvious optimization if it can be done efficiently. -- greg From Dhanaraj.M@Sun.COM Sat Apr 22 07:15:07 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 9510B11F6AE2 for ; Sat, 22 Apr 2006 04:15:23 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id viXhy3rZL6D2 for ; Sat, 22 Apr 2006 04:15:16 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id A9A5511F692D for ; Sat, 22 Apr 2006 04:15:15 -0300 (ADT) Received: from sineb-mail-2.sun.com (sineb-mail-2.sun.com [192.18.19.7]) by svr4.postgresql.org (Postfix) with ESMTP id 43D1C5AFA5A for ; Sat, 22 Apr 2006 07:15:14 +0000 (GMT) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-2.sun.com (8.12.10+Sun/8.12.9) with ESMTP id k3M7F8FV029064 for ; Sat, 22 Apr 2006 15:15:10 +0800 (SGT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0IY40050142T0C00@mail-apac.sun.com> (original mail from Dhanaraj.M@Sun.COM) for pgsql-hackers@postgresql.org; Sat, 22 Apr 2006 15:15:08 +0800 (SGT) Received: from [129.158.226.138] by mail-apac.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0IY400DD545736LG@mail-apac.sun.com> for pgsql-hackers@postgresql.org; Sat, 22 Apr 2006 15:15:08 +0800 (SGT) Date: Sat, 22 Apr 2006 12:45:07 +0530 From: Dhanaraj M Subject: TODO items.. To: pgsql-hackers@postgresql.org Message-id: <4449D7FB.905@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050322) X-Archive-Number: 200604/794 X-Sequence-Number: 82517 I saw the following in the TODO list. I am currently trying to work on them. I could not understand clearly what needs to be done. Can anybody give me the details for the following so that I can work on? clients-psql ========= 1. Have psql show current values for a sequence 2. Fix psql's display of schema information (Neil) Please explain me the current feature that is supported and expected out of it. Thanks Dhanaraj From alvherre@commandprompt.com Sat Apr 22 15:24:45 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id C8DF211F6263 for ; Sat, 22 Apr 2006 12:24:49 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 1.72 X-Spam-Level: * X-Spam-Status: No, score=1.72 required=5 tests=[AWL=-0.199, DNS_FROM_RFC_ABUSE=0.479, DNS_FROM_RFC_POST=1.44] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id g1oClVju2nNS for ; Sat, 22 Apr 2006 12:24:47 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx1.surnet.cl (mx1.surnet.cl [216.155.73.180]) by postgresql.org (Postfix) with ESMTP id 9C13C11F65F5 for ; Sat, 22 Apr 2006 12:24:46 -0300 (ADT) Received: from unknown (HELO cluster.surnet.cl) ([216.155.73.165]) by mx1.surnet.cl with ESMTP; 22 Apr 2006 11:24:46 -0400 X-IronPort-AV: i="4.04,146,1144036800"; d="scan'208"; a="55778262:sNHT17798468" Received: from alvh.no-ip.org (200.126.99.223) by cluster.surnet.cl (7.0.043) (authenticated as alvherre@surnet.cl) id 443B7DDC00183762; Sat, 22 Apr 2006 11:24:45 -0400 Received: by alvh.no-ip.org (Postfix, from userid 1000) id 3C91BC30F8E; Sat, 22 Apr 2006 11:24:45 -0400 (CLT) Date: Sat, 22 Apr 2006 11:24:45 -0400 From: Alvaro Herrera To: Dhanaraj M Cc: pgsql-hackers@postgresql.org Subject: Re: TODO items.. Message-ID: <20060422152445.GB12686@surnet.cl> Mail-Followup-To: Dhanaraj M , pgsql-hackers@postgresql.org References: <4449D7FB.905@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4449D7FB.905@sun.com> User-Agent: Mutt/1.5.11+cvs20060403 X-Archive-Number: 200604/797 X-Sequence-Number: 82520 Dhanaraj M wrote: > I saw the following in the TODO list. I am currently trying to work on them. > I could not understand clearly what needs to be done. Can anybody give me > the details for the following so that I can work on? > > clients-psql > ========= > 1. Have psql show current values for a sequence This one means when you do a \dt of a sequence, add a column to display the current value. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. From pgdev@xs4all.nl Sat Apr 22 15:37:28 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 97AA411F653F for ; Sat, 22 Apr 2006 12:38:08 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.528 X-Spam-Level: X-Spam-Status: No, score=-2.528 required=5 tests=[AWL=0.071, BAYES_00=-2.599] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id jx3N6NMA16hB for ; Sat, 22 Apr 2006 12:38:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from smtp-vbr6.xs4all.nl (smtp-vbr6.xs4all.nl [194.109.24.26]) by postgresql.org (Postfix) with ESMTP id 9BDF111F68D2 for ; Sat, 22 Apr 2006 12:38:00 -0300 (ADT) Received: from [192.168.1.4] (213-84-4-128.adsl.xs4all.nl [213.84.4.128]) (authenticated bits=0) by smtp-vbr6.xs4all.nl (8.13.6/8.13.6) with ESMTP id k3MFbNEC090259; Sat, 22 Apr 2006 17:37:52 +0200 (CEST) (envelope-from pgdev@xs4all.nl) Subject: Re: TODO items.. From: Gevik Babakhani To: Alvaro Herrera Cc: Dhanaraj M , pgsql-hackers@postgresql.org In-Reply-To: <20060422152445.GB12686@surnet.cl> References: <4449D7FB.905@sun.com> <20060422152445.GB12686@surnet.cl> Content-Type: text/plain Date: Sat, 22 Apr 2006 17:37:28 +0200 Message-Id: <1145720248.29124.2.camel@voyager.truesoftware.net> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 (2.6.1-1.fc5.2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner X-Archive-Number: 200604/798 X-Sequence-Number: 82521 > This one means when you do a \dt of a sequence, add a column to display > the current value. > Perhaps this one will be tricky because you will never be sure to get the last sequence number when you query for it. The number could change the moment the query is finished. From kleptog@svana.org Sat Apr 22 15:57:27 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id B240611F6971 for ; Sat, 22 Apr 2006 12:57:43 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.358 X-Spam-Level: X-Spam-Status: No, score=-2.358 required=5 tests=[AWL=0.241, BAYES_00=-2.599] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id 7hEruyw42z6e for ; Sat, 22 Apr 2006 12:57:35 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svana.org (svana.org [125.62.94.225]) by postgresql.org (Postfix) with ESMTP id 5AE2211F628D for ; Sat, 22 Apr 2006 12:57:35 -0300 (ADT) Received: from kleptog by svana.org with local (Exim 4.50) id 1FXKUB-0002n9-DM; Sun, 23 Apr 2006 01:57:27 +1000 Date: Sat, 22 Apr 2006 17:57:27 +0200 From: Martijn van Oosterhout To: Gevik Babakhani Cc: Alvaro Herrera , Dhanaraj M , pgsql-hackers@postgresql.org Subject: Re: TODO items.. Message-ID: <20060422155727.GG7398@svana.org> Reply-To: Martijn van Oosterhout References: <4449D7FB.905@sun.com> <20060422152445.GB12686@surnet.cl> <1145720248.29124.2.camel@voyager.truesoftware.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qoTlaiD+Y2fIM3Ll" Content-Disposition: inline In-Reply-To: <1145720248.29124.2.camel@voyager.truesoftware.net> X-PGP-Key-ID: Length=1024; ID=0x0DC67BE6 X-PGP-Key-Fingerprint: 295F A899 A81A 156D B522 48A7 6394 F08A 0DC6 7BE6 X-PGP-Key-URL: User-Agent: Mutt/1.5.9i X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kleptog@svana.org X-SA-Exim-Scanned: No (on svana.org); SAEximRunCond expanded to false X-Archive-Number: 200604/799 X-Sequence-Number: 82522 --qoTlaiD+Y2fIM3Ll Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Apr 22, 2006 at 05:37:28PM +0200, Gevik Babakhani wrote: >=20 > > This one means when you do a \dt of a sequence, add a column to display > > the current value. > >=20 >=20 > Perhaps this one will be tricky because you will never be sure to get > the last sequence number when you query for it. The number could change > the moment the query is finished. So could the structure of a table or the definition of a function. That's just a fact of life. Doesn't change the fact that it'd be useful. You need nextval() to actually get a useful value for queries... Have a nice day, --=20 Martijn van Oosterhout http://svana.org/kleptog/ > From each according to his ability. To each according to his ability to l= itigate. --qoTlaiD+Y2fIM3Ll Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFESlJnIB7bNG8LQkwRAgN9AJ9b0k3OTT0tw5g7phyD4IEdK/lGvQCghAOb 18Smohu8I51DVj+e6gN5ewE= =e9qc -----END PGP SIGNATURE----- --qoTlaiD+Y2fIM3Ll-- From pgman@candle.pha.pa.us Sat Apr 22 16:08:17 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 1EF1F11F671D for ; Sat, 22 Apr 2006 13:08:21 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.113 X-Spam-Level: X-Spam-Status: No, score=0.113 required=5 tests=[AWL=0.113] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id ZcVPPoJPUQbO for ; Sat, 22 Apr 2006 13:08:18 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from candle.pha.pa.us (candle.pha.pa.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 35A7C11F66D5 for ; Sat, 22 Apr 2006 13:08:17 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id k3MG8HG00340; Sat, 22 Apr 2006 12:08:17 -0400 (EDT) From: Bruce Momjian Message-Id: <200604221608.k3MG8HG00340@candle.pha.pa.us> Subject: Re: TODO items.. In-Reply-To: <4449D7FB.905@sun.com> To: Dhanaraj M Date: Sat, 22 Apr 2006 12:08:17 -0400 (EDT) CC: pgsql-hackers@postgresql.org X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200604/800 X-Sequence-Number: 82523 Dhanaraj M wrote: > I saw the following in the TODO list. I am currently trying to work on them. > I could not understand clearly what needs to be done. Can anybody give me > the details for the following so that I can work on? > > clients-psql > ========= > 1. Have psql show current values for a sequence Already answered. > 2. Fix psql's display of schema information (Neil) > > Please explain me the current feature that is supported and expected > out of it. Yes, this item was unclear. I used text suggested by the author: http://archives.postgresql.org/pgsql-hackers/2004-12/msg00094.php but that was not clear. TODO is now: o Fix psql's \dn for various schema combinations (Neil) http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php with a URL that has the details. Thanks for pointing out the problem. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + From tgl@sss.pgh.pa.us Sat Apr 22 17:34:42 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 10B7611F6A9C for ; Sat, 22 Apr 2006 14:34:47 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: 0.121 X-Spam-Level: X-Spam-Status: No, score=0.121 required=5 tests=[AWL=0.121] Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id Bx5mw-Th--Bp for ; Sat, 22 Apr 2006 14:34:44 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 937CE11F6AC5 for ; Sat, 22 Apr 2006 14:34:44 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k3MHYgM6007721; Sat, 22 Apr 2006 13:34:42 -0400 (EDT) To: Bruce Momjian cc: Dhanaraj M , pgsql-hackers@postgresql.org Subject: Re: TODO items.. In-reply-to: <200604221608.k3MG8HG00340@candle.pha.pa.us> References: <200604221608.k3MG8HG00340@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Sat, 22 Apr 2006 12:08:17 -0400" Date: Sat, 22 Apr 2006 13:34:42 -0400 Message-ID: <7720.1145727282@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200604/803 X-Sequence-Number: 82526 Bruce Momjian writes: > but that was not clear. TODO is now: > o Fix psql's \dn for various schema combinations (Neil) > http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php > with a URL that has the details. Thanks for pointing out the problem. You might want to also include a link to the thread start, http://archives.postgresql.org/pgsql-hackers/2004-10/msg00989.php because the above message doesn't link there (I think our mail archiver has trouble with following threads across month boundaries). Also, the TODO item could be worded * Make psql's \d commands more consistent because that's really what Neil is on about ... regards, tom lane From pgman@candle.pha.pa.us Sat Apr 22 18:17:56 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id BEBCF11F8CE5 for ; Sat, 22 Apr 2006 15:18:04 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.457 X-Spam-Level: X-Spam-Status: No, score=-2.457 required=5 tests=[AWL=0.144, BAYES_00=-2.599, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id ddhWKPc+xct0 for ; Sat, 22 Apr 2006 15:18:01 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from candle.pha.pa.us (candle.pha.pa.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id 3A2E211F60B3 for ; Sat, 22 Apr 2006 15:17:58 -0300 (ADT) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id k3MIHub07730; Sat, 22 Apr 2006 14:17:56 -0400 (EDT) From: Bruce Momjian Message-Id: <200604221817.k3MIHub07730@candle.pha.pa.us> Subject: Re: TODO items.. In-Reply-To: <7720.1145727282@sss.pgh.pa.us> To: Tom Lane Date: Sat, 22 Apr 2006 14:17:56 -0400 (EDT) CC: Dhanaraj M , pgsql-hackers@postgresql.org X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200604/804 X-Sequence-Number: 82527 OK, done. --------------------------------------------------------------------------- Tom Lane wrote: > Bruce Momjian writes: > > but that was not clear. TODO is now: > > o Fix psql's \dn for various schema combinations (Neil) > > http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php > > with a URL that has the details. Thanks for pointing out the problem. > > You might want to also include a link to the thread start, > http://archives.postgresql.org/pgsql-hackers/2004-10/msg00989.php > > because the above message doesn't link there (I think our mail archiver > has trouble with following threads across month boundaries). > > Also, the TODO item could be worded > > * Make psql's \d commands more consistent > > because that's really what Neil is on about ... > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend > -- Bruce Momjian http://candle.pha.pa.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + From xzilla@users.sourceforge.net Sun Apr 23 15:06:30 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D921A11F9650 for ; Sun, 23 Apr 2006 12:06:40 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 35410-03 for ; Sun, 23 Apr 2006 12:06:38 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from eastrmmtao05.cox.net (eastrmmtao05.cox.net [68.230.240.34]) by postgresql.org (Postfix) with ESMTP id C796111F9653 for ; Sun, 23 Apr 2006 12:06:37 -0300 (ADT) Received: from [192.168.0.8] (really [24.136.35.185]) by eastrmmtao05.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060423150636.RWGN29406.eastrmmtao05.cox.net@[192.168.0.8]>; Sun, 23 Apr 2006 11:06:36 -0400 From: Robert Treat To: pgsql-hackers@postgresql.org Subject: Re: TODO items.. Date: Sun, 23 Apr 2006 11:06:30 -0400 User-Agent: KMail/1.8.3 Cc: Tom Lane , Bruce Momjian , Dhanaraj M References: <200604221608.k3MG8HG00340@candle.pha.pa.us> <7720.1145727282@sss.pgh.pa.us> In-Reply-To: <7720.1145727282@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604231106.31303.xzilla@users.sourceforge.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/819 X-Sequence-Number: 82542 On Saturday 22 April 2006 13:34, Tom Lane wrote: > Also, the TODO item could be worded > > * Make psql's \d commands more consistent > > because that's really what Neil is on about ... > like making \df only show user functions and \dfS show system functions, like all the other objects? :-) -- Robert Treat Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL From xzilla@users.sourceforge.net Sun Apr 23 15:07:29 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 13FAA11F9655 for ; Sun, 23 Apr 2006 12:07:40 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 32118-02 for ; Sun, 23 Apr 2006 12:07:36 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from eastrmmtao01.cox.net (eastrmmtao01.cox.net [68.230.240.38]) by postgresql.org (Postfix) with ESMTP id BE56711F9652 for ; Sun, 23 Apr 2006 12:07:35 -0300 (ADT) Received: from [192.168.0.8] (really [24.136.35.185]) by eastrmmtao01.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060423150735.EJBG18061.eastrmmtao01.cox.net@[192.168.0.8]>; Sun, 23 Apr 2006 11:07:35 -0400 From: Robert Treat To: pgsql-hackers@postgresql.org Subject: Re: TODO items.. Date: Sun, 23 Apr 2006 11:07:29 -0400 User-Agent: KMail/1.8.3 Cc: Alvaro Herrera , Dhanaraj M References: <4449D7FB.905@sun.com> <20060422152445.GB12686@surnet.cl> In-Reply-To: <20060422152445.GB12686@surnet.cl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604231107.30050.xzilla@users.sourceforge.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/820 X-Sequence-Number: 82543 On Saturday 22 April 2006 11:24, Alvaro Herrera wrote: > Dhanaraj M wrote: > > I saw the following in the TODO list. I am currently trying to work on > > them. I could not understand clearly what needs to be done. Can anybody > > give me the details for the following so that I can work on? > > > > clients-psql > > ========= > > 1. Have psql show current values for a sequence > > This one means when you do a \dt of a sequence, add a column to display > the current value. Um, I think you meant \ds right ? -- Robert Treat Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL From alvherre@commandprompt.com Sun Apr 23 15:42:10 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 1AA1111F6085 for ; Sun, 23 Apr 2006 12:42:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 47046-02 for ; Sun, 23 Apr 2006 12:42:12 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mx1.surnet.cl (mx1.surnet.cl [216.155.73.180]) by postgresql.org (Postfix) with ESMTP id 49E0C11F607B for ; Sun, 23 Apr 2006 12:42:11 -0300 (ADT) Received: from unknown (HELO cluster.surnet.cl) ([216.155.73.165]) by mx1.surnet.cl with ESMTP; 23 Apr 2006 11:42:11 -0400 X-IronPort-AV: i="4.04,149,1144036800"; d="scan'208"; a="55966083:sNHT18299624" Received: from alvh.no-ip.org (200.126.99.223) by cluster.surnet.cl (7.0.043) (authenticated as alvherre@surnet.cl) id 443B7DDC001985CC; Sun, 23 Apr 2006 11:42:10 -0400 Received: by alvh.no-ip.org (Postfix, from userid 1000) id A0F5DC30F8E; Sun, 23 Apr 2006 11:42:10 -0400 (CLT) Date: Sun, 23 Apr 2006 11:42:10 -0400 From: Alvaro Herrera To: Robert Treat Cc: pgsql-hackers@postgresql.org, Dhanaraj M Subject: Re: TODO items.. Message-ID: <20060423154210.GB3381@surnet.cl> Mail-Followup-To: Robert Treat , pgsql-hackers@postgresql.org, Dhanaraj M References: <4449D7FB.905@sun.com> <20060422152445.GB12686@surnet.cl> <200604231107.30050.xzilla@users.sourceforge.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200604231107.30050.xzilla@users.sourceforge.net> User-Agent: Mutt/1.5.11+cvs20060403 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/821 X-Sequence-Number: 82544 Robert Treat wrote: > On Saturday 22 April 2006 11:24, Alvaro Herrera wrote: > > Dhanaraj M wrote: > > > I saw the following in the TODO list. I am currently trying to work on > > > them. I could not understand clearly what needs to be done. Can anybody > > > give me the details for the following so that I can work on? > > > > > > clients-psql > > > ========= > > > 1. Have psql show current values for a sequence > > > > This one means when you do a \dt of a sequence, add a column to display > > the current value. > > Um, I think you meant \ds right ? Whatever. I don't display sequences a lot myself ... -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support From sfrost@snowman.net Sun Apr 23 15:55:40 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 565E411F65DB for ; Sun, 23 Apr 2006 12:54:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 49221-02 for ; Sun, 23 Apr 2006 12:54:26 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from ns.snowman.net (ns.snowman.net [66.92.160.21]) by postgresql.org (Postfix) with ESMTP id BF6A511F628C for ; Sun, 23 Apr 2006 12:54:25 -0300 (ADT) Received: by ns.snowman.net (Postfix, from userid 1000) id DFF5017AD3; Sun, 23 Apr 2006 11:55:40 -0400 (EDT) Date: Sun, 23 Apr 2006 11:55:40 -0400 From: Stephen Frost To: Robert Treat Cc: pgsql-hackers@postgresql.org, Tom Lane , Bruce Momjian , Dhanaraj M Subject: Re: TODO items.. Message-ID: <20060423155540.GV4474@ns.snowman.net> Mail-Followup-To: Robert Treat , pgsql-hackers@postgresql.org, Tom Lane , Bruce Momjian , Dhanaraj M References: <200604221608.k3MG8HG00340@candle.pha.pa.us> <7720.1145727282@sss.pgh.pa.us> <200604231106.31303.xzilla@users.sourceforge.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cFU7Ny1L0ShjNgMX" Content-Disposition: inline In-Reply-To: <200604231106.31303.xzilla@users.sourceforge.net> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.4.24ns.3.0 (i686) X-Uptime: 11:53:25 up 316 days, 7:59, 11 users, load average: 0.43, 0.18, 0.05 User-Agent: Mutt/1.5.11 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200604/822 X-Sequence-Number: 82545 --cFU7Ny1L0ShjNgMX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Robert Treat (xzilla@users.sourceforge.net) wrote: > On Saturday 22 April 2006 13:34, Tom Lane wrote: > > Also, the TODO item could be worded > > > > * Make psql's \d commands more consistent > > > > because that's really what Neil is on about ... > > >=20 > like making \df only show user functions and \dfS show system functions, = like=20 > all the other objects? :-) How about also having it show the owner (instead of having to use \df+ which gets huge...) and the permissions... Or perhaps have a seperate \dfp or something to get that information. It's annoying to have to either query the catalog directly or look through \df+ for why I can't drop a given function. Thanks, Stephen --cFU7Ny1L0ShjNgMX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFES6N8rzgMPqB3kigRAkT7AJ9Hh5Z44fG5RZJGHzRmE4nOqErNBQCeIpjr CYzTiuAxVd7YyIQrVJ2CoVU= =QZgo -----END PGP SIGNATURE----- --cFU7Ny1L0ShjNgMX-- From xzilla@users.sourceforge.net Sun Apr 23 20:08:01 2006 X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 6A92A11F60E5 for ; Sun, 23 Apr 2006 17:09:25 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 87981-03 for ; Sun, 23 Apr 2006 17:08:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from eastrmmtao06.cox.net (eastrmmtao06.cox.net [68.230.240.33]) by postgresql.org (Postfix) with ESMTP id 2E49711F61CF for ; Sun, 23 Apr 2006 17:08:08 -0300 (ADT) Received: from [192.168.0.8] (really [24.136.35.185]) by eastrmmtao06.cox.net (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP id <20060423200807.LMXY18886.eastrmmtao06.cox.net@[192.168.0.8]>; Sun, 23 Apr 2006 16:08:07 -0400 From: Robert Treat To: Alvaro Herrera Subject: Re: TODO items.. Date: Sun, 23 Apr 2006 16:08:01 -0400 User-Agent: KMail/1.8.3 Cc: pgsql-hackers@postgresql.org, Dhanaraj M References: <4449D7FB.905@sun.com> <200604231107.30050.xzilla@users.sourceforge.net> <20060423154210.GB3381@surnet.cl> In-Reply-To: <20060423154210.GB3381@surnet.cl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200604231608.02042.xzilla@users.sourceforge.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/828 X-Sequence-Number: 82551 On Sunday 23 April 2006 11:42, Alvaro Herrera wrote: > Robert Treat wrote: > > On Saturday 22 April 2006 11:24, Alvaro Herrera wrote: > > > Dhanaraj M wrote: > > > > I saw the following in the TODO list. I am currently trying to work > > > > on them. I could not understand clearly what needs to be done. Can > > > > anybody give me the details for the following so that I can work on? > > > > > > > > clients-psql > > > > ========= > > > > 1. Have psql show current values for a sequence > > > > > > This one means when you do a \dt of a sequence, add a column to display > > > the current value. > > > > Um, I think you meant \ds right ? > > Whatever. I don't display sequences a lot myself ... :-) I double checked because I wasn't sure myself, but figured it was best to clarify rather than risk confusing the noobs. :-) -- Robert Treat Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL From jcasanov@systemguards.com.ec Thu Jul 2 21:28:11 2009 Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 278FE6333FB for ; Thu, 2 Jul 2009 18:28:29 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 28709-10 for ; Thu, 2 Jul 2009 18:28:28 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f211.google.com (mail-bw0-f211.google.com [209.85.218.211]) by mail.postgresql.org (Postfix) with ESMTP id 0787E6333B2 for ; Thu, 2 Jul 2009 18:28:27 -0300 (ADT) Received: by bwz7 with SMTP id 7so1979356bwz.19 for ; Thu, 02 Jul 2009 14:28:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.213.10 with SMTP id p10mr269931muq.132.1246570106169; Thu, 02 Jul 2009 14:28:26 -0700 (PDT) From: Jaime Casanova Date: Thu, 2 Jul 2009 16:28:11 -0500 Message-ID: <3073cc9b0907021428i35432ec8j55b25f951da116e8@mail.gmail.com> Subject: TODO items To: PostgreSQL-development Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200907/168 X-Sequence-Number: 140790 Hi, I guess todo items marked as [D] (Done) should be removed now... right? --=20 Atentamente, Jaime Casanova Soporte y capacitaci=C3=B3n de PostgreSQL Asesor=C3=ADa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 From alvherre@commandprompt.com Thu Jul 2 21:29:42 2009 Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 225BB6333FB for ; Thu, 2 Jul 2009 18:29:48 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 53910-04 for ; Thu, 2 Jul 2009 18:29:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by mail.postgresql.org (Postfix) with ESMTP id B17766333B2 for ; Thu, 2 Jul 2009 18:29:46 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-220-118-158.bk10-dsl.surnet.cl [201.220.118.158]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id n62LcAU5013818 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jul 2009 14:38:12 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 8A555D4192; Thu, 2 Jul 2009 17:29:42 -0400 (CLT) Date: Thu, 2 Jul 2009 17:29:42 -0400 From: Alvaro Herrera To: Jaime Casanova Cc: PostgreSQL-development Subject: Re: TODO items Message-ID: <20090702212942.GM4698@alvh.no-ip.org> References: <3073cc9b0907021428i35432ec8j55b25f951da116e8@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3073cc9b0907021428i35432ec8j55b25f951da116e8@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 02 Jul 2009 14:38:12 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=AWL=0.000 X-Spam-Level: X-Archive-Number: 200907/169 X-Sequence-Number: 140791 Jaime Casanova wrote: > Hi, > > I guess todo items marked as [D] (Done) should be removed now... right? Would there be some value in creating a new page TodoDone84 and moving those items to it? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. From jd@commandprompt.com Thu Jul 2 21:35:08 2009 Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 9A68062F51F for ; Thu, 2 Jul 2009 18:35:15 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 31100-01 for ; Thu, 2 Jul 2009 18:35:14 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by mail.postgresql.org (Postfix) with ESMTP id 63FFA6340E4 for ; Thu, 2 Jul 2009 18:35:14 -0300 (ADT) Received: from [75.142.153.203] (75-142-153-203.dhcp.or.charter.com [75.142.153.203] (may be forged)) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id n62Lha23014159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jul 2009 14:43:37 -0700 Subject: Re: TODO items From: "Joshua D. Drake" Reply-To: jd@commandprompt.com To: Alvaro Herrera Cc: Jaime Casanova , PostgreSQL-development In-Reply-To: <20090702212942.GM4698@alvh.no-ip.org> References: <3073cc9b0907021428i35432ec8j55b25f951da116e8@mail.gmail.com> <20090702212942.GM4698@alvh.no-ip.org> Content-Type: text/plain Organization: Command Prompt, Inc. Date: Thu, 02 Jul 2009 14:35:08 -0700 Message-Id: <1246570508.17276.25.camel@jd-laptop.pragmaticzealot.org> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 02 Jul 2009 14:43:37 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200907/171 X-Sequence-Number: 140793 On Thu, 2009-07-02 at 17:29 -0400, Alvaro Herrera wrote: > Jaime Casanova wrote: > > Hi, > > > > I guess todo items marked as [D] (Done) should be removed now... right? > > Would there be some value in creating a new page TodoDone84 and moving > those items to it? For historical record I could see benefit. Joshua D. Drake > > -- > Alvaro Herrera http://www.CommandPrompt.com/ > The PostgreSQL Company - Command Prompt, Inc. > -- PostgreSQL - XMPP: jdrake@jabber.postgresql.org Consulting, Development, Support, Training 503-667-4564 - http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997 From andrew@dunslane.net Thu Jul 2 21:43:43 2009 Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 24C2D6333B2 for ; Thu, 2 Jul 2009 18:43:52 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 56488-07 for ; Thu, 2 Jul 2009 18:43:45 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from alexis.jtlnet.com (alexis.jtlnet.com [69.36.9.81]) by mail.postgresql.org (Postfix) with ESMTP id A475962F51F for ; Thu, 2 Jul 2009 18:43:50 -0300 (ADT) Received: from [192.168.10.103] (cpe-075-177-154-027.nc.res.rr.com [::ffff:75.177.154.27]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by alexis.jtlnet.com with esmtp; Thu, 02 Jul 2009 17:42:51 -0400 id 00087DC2.4A4D29DC.00002FE0 Message-ID: <4A4D2A0F.3000607@dunslane.net> Date: Thu, 02 Jul 2009 17:43:43 -0400 From: Andrew Dunstan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text SeaMonkey/1.0.9 MIME-Version: 1.0 To: jd@commandprompt.com CC: Alvaro Herrera , Jaime Casanova , PostgreSQL-development Subject: Re: TODO items References: <3073cc9b0907021428i35432ec8j55b25f951da116e8@mail.gmail.com> <20090702212942.GM4698@alvh.no-ip.org> <1246570508.17276.25.camel@jd-laptop.pragmaticzealot.org> In-Reply-To: <1246570508.17276.25.camel@jd-laptop.pragmaticzealot.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.072 tagged_above=0 required=5 tests=AWL=0.072 X-Spam-Level: X-Archive-Number: 200907/174 X-Sequence-Number: 140796 Joshua D. Drake wrote: > On Thu, 2009-07-02 at 17:29 -0400, Alvaro Herrera wrote: > >> Jaime Casanova wrote: >> >>> Hi, >>> >>> I guess todo items marked as [D] (Done) should be removed now... right? >>> >> Would there be some value in creating a new page TodoDone84 and moving >> those items to it? >> > > For historical record I could see benefit. > > Doesn't the wiki keep a page history? I don't see much point in keeping the old items in a current page. cheers andrew From tgl@sss.pgh.pa.us Thu Jul 2 21:50:29 2009 Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 5A836633D78 for ; Thu, 2 Jul 2009 18:50:33 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 58027-06 for ; Thu, 2 Jul 2009 18:50:26 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 1762B62F51F for ; Thu, 2 Jul 2009 18:50:31 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id n62LoTDT020856; Thu, 2 Jul 2009 17:50:30 -0400 (EDT) To: Alvaro Herrera cc: Jaime Casanova , PostgreSQL-development Subject: Re: TODO items In-reply-to: <20090702212942.GM4698@alvh.no-ip.org> References: <3073cc9b0907021428i35432ec8j55b25f951da116e8@mail.gmail.com> <20090702212942.GM4698@alvh.no-ip.org> Comments: In-reply-to Alvaro Herrera message dated "Thu, 02 Jul 2009 17:29:42 -0400" Date: Thu, 02 Jul 2009 17:50:29 -0400 Message-ID: <20855.1246571429@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.085 tagged_above=0 required=5 tests=AWL=0.085 X-Spam-Level: X-Archive-Number: 200907/175 X-Sequence-Number: 140797 Alvaro Herrera writes: > Jaime Casanova wrote: >> I guess todo items marked as [D] (Done) should be removed now... right? > Would there be some value in creating a new page TodoDone84 and moving > those items to it? In the past we've figured that old TODO versions could be retrieved from CVS history. While that's still possible in the wiki environment, it might be worth saving the old entries in a more easily accessible fashion. regards, tom lane From alvherre@commandprompt.com Thu Jul 2 21:52:21 2009 Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id B0BA262F51F for ; Thu, 2 Jul 2009 18:53:42 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 58574-07 for ; Thu, 2 Jul 2009 18:53:35 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by mail.postgresql.org (Postfix) with ESMTP id 3649662E67F for ; Thu, 2 Jul 2009 18:53:40 -0300 (ADT) Received: from perhan.alvh.no-ip.org (201-220-118-158.bk10-dsl.surnet.cl [201.220.118.158]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id n62M0ngB015416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Jul 2009 15:00:52 -0700 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 8D4AAD4192; Thu, 2 Jul 2009 17:52:21 -0400 (CLT) Date: Thu, 2 Jul 2009 17:52:21 -0400 From: Alvaro Herrera To: Andrew Dunstan Cc: jd@commandprompt.com, Jaime Casanova , PostgreSQL-development Subject: Re: TODO items Message-ID: <20090702215221.GO4698@alvh.no-ip.org> References: <3073cc9b0907021428i35432ec8j55b25f951da116e8@mail.gmail.com> <20090702212942.GM4698@alvh.no-ip.org> <1246570508.17276.25.camel@jd-laptop.pragmaticzealot.org> <4A4D2A0F.3000607@dunslane.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A4D2A0F.3000607@dunslane.net> User-Agent: Mutt/1.5.18 (2008-05-17) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Thu, 02 Jul 2009 15:00:53 -0700 (PDT) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=AWL=0.000 X-Spam-Level: X-Archive-Number: 200907/177 X-Sequence-Number: 140799 Andrew Dunstan wrote: > > > Joshua D. Drake wrote: >> On Thu, 2009-07-02 at 17:29 -0400, Alvaro Herrera wrote: >> >>> Jaime Casanova wrote: >>> >>>> I guess todo items marked as [D] (Done) should be removed now... right? >>>> >>> Would there be some value in creating a new page TodoDone84 and moving >>> those items to it? >> >> For historical record I could see benefit. > > Doesn't the wiki keep a page history? Yes, but it is not as convenient. > I don't see much point in keeping the old items in a current page. It is useful to point out to people: look at all the things we did in 8.4! -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support From jcasanov@systemguards.com.ec Thu Jul 2 21:54:52 2009 Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 263ED62F51F for ; Thu, 2 Jul 2009 18:55:10 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 35168-09 for ; Thu, 2 Jul 2009 18:55:09 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-fx0-f209.google.com (mail-fx0-f209.google.com [209.85.220.209]) by mail.postgresql.org (Postfix) with ESMTP id 065B762E67F for ; Thu, 2 Jul 2009 18:55:08 -0300 (ADT) Received: by fxm5 with SMTP id 5so925980fxm.19 for ; Thu, 02 Jul 2009 14:55:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.103.214.8 with SMTP id r8mr314007muq.12.1246571707093; Thu, 02 Jul 2009 14:55:07 -0700 (PDT) In-Reply-To: <20855.1246571429@sss.pgh.pa.us> References: <3073cc9b0907021428i35432ec8j55b25f951da116e8@mail.gmail.com> <20090702212942.GM4698@alvh.no-ip.org> <20855.1246571429@sss.pgh.pa.us> From: Jaime Casanova Date: Thu, 2 Jul 2009 16:54:52 -0500 Message-ID: <3073cc9b0907021454l6eb6fb95vd6698c8274ee47ba@mail.gmail.com> Subject: Re: TODO items To: Tom Lane Cc: Alvaro Herrera , PostgreSQL-development Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200907/178 X-Sequence-Number: 140800 On Thu, Jul 2, 2009 at 4:50 PM, Tom Lane wrote: > Alvaro Herrera writes: >> Jaime Casanova wrote: >>> I guess todo items marked as [D] (Done) should be removed now... right? > >> Would there be some value in creating a new page TodoDone84 and moving >> those items to it? > > In the past we've figured that old TODO versions could be retrieved > from CVS history. =C2=A0While that's still possible in the wiki environme= nt, > it might be worth saving the old entries in a more easily accessible > fashion. > We want to use the same format/sections like in the TODO? --=20 Atentamente, Jaime Casanova Soporte y capacitaci=C3=B3n de PostgreSQL Asesor=C3=ADa y desarrollo de sistemas Guayaquil - Ecuador Cel. +59387171157 From tgl@sss.pgh.pa.us Thu Jul 2 22:04:23 2009 Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id CCC0B6333B2 for ; Thu, 2 Jul 2009 19:04:30 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 61638-02 for ; Thu, 2 Jul 2009 19:04:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 7E3966322AC for ; Thu, 2 Jul 2009 19:04:29 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id n62M4OQA021385; Thu, 2 Jul 2009 18:04:24 -0400 (EDT) To: Jaime Casanova cc: Alvaro Herrera , PostgreSQL-development Subject: Re: TODO items In-reply-to: <3073cc9b0907021454l6eb6fb95vd6698c8274ee47ba@mail.gmail.com> References: <3073cc9b0907021428i35432ec8j55b25f951da116e8@mail.gmail.com> <20090702212942.GM4698@alvh.no-ip.org> <20855.1246571429@sss.pgh.pa.us> <3073cc9b0907021454l6eb6fb95vd6698c8274ee47ba@mail.gmail.com> Comments: In-reply-to Jaime Casanova message dated "Thu, 02 Jul 2009 16:54:52 -0500" Date: Thu, 02 Jul 2009 18:04:23 -0400 Message-ID: <21384.1246572263@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.085 tagged_above=0 required=5 tests=AWL=0.085 X-Spam-Level: X-Archive-Number: 200907/179 X-Sequence-Number: 140801 Jaime Casanova writes: > We want to use the same format/sections like in the TODO? Sure, why not? Just copy the page and strip out the not-done items. No reason to think hard here. regards, tom lane