6.6 items
I have updated the TODO list, rearranging it. Here is the top of the
"Enhancements" list:
* Add referential integrity
* Add OUTER joins, left and right(Thomas)
* Allow long tuples by chaining or auto-storing outside db (chaining,large objs)
* Fix memory leak for expressions?, aggregates?
And the top of "Performance" is:
* Allow transaction commits with rollback with no-fsync performance
* Prevent fsync in SELECT-only queries
This should help. Did I get all the big items just discussed?
---------------------------------------------------------------------------
TODO list for PostgreSQL
========================
Last updated: Sun Jun 6 22:08:59 EDT 1999
Current maintainer: Bruce Momjian (maillist@candle.pha.pa.us)
The most recent version of this document can be viewed at
the PostgreSQL WWW site, http://www.postgreSQL.org.
A dash(-) marks changes to be in the next release.
Developers who have claimed items are:
-------------------------------------
* Billy is Billy G. Allie <Bill.Allie@mug.org>
* Brook is Brook Milligan <brook@trillium.NMSU.Edu>
* Bruce is Bruce Momjian<maillist@candle.pha.pa.us>
* Bryan is Bryan Henderson<bryanh@giraffe.netgate.net>
* D'Arcy is D'Arcy J.M. Cain <darcy@druid.net>
* David is David Hartwig <daveh@insightdist.com>
* Edmund is Edmund Mergl <E.Mergl@bawue.de>
* Goran is Goran Thyni <goran@kyla.kiruna.se>
* Hiroshi is Hiroshi Inoue<Inoue@tpf.co.jp>
* Jan is Jan Wieck <wieck@sapserv.debis.de>
* Marc is Marc Fournier <scrappy@hub.org>
* Massimo Dal Zotto <dz@cs.unitn.it>
* Michael is Michael Meskes <meskes@debian.org>
* Oleg is Oleg Bartunov <oleg@sai.msu.su>
* Peter is Peter T Mount <peter@retep.org.uk>
* Stefan Simkovics <ssimkovi@rainbow.studorg.tuwien.ac.at>
* Tatsuo is Tatsuo Ishii <t-ishii@sra.co.jp>
* Tom is Tom Lane <tgl@sss.pgh.pa.us>
* Thomas is Thomas Lockhart <lockhart@alumni.caltech.edu>
* TomH is Tom I Helbekkmo <tih@Hamartun.Priv.NO>
* Vadim is "Vadim B. Mikheev" <vadim@krs.ru>
RELIABILITY
-----------
* Overhaul mdmgr/smgr to fix double unlinking and double opens, cleanup
* Overhaul bufmgr/lockmgr/transaction manager
* Remove EXTEND?
* Tables that start with xinv confused to be large objects
* Two and three dimensional arrays display improperly, missing {}
* Select a[1] FROM test fails, it needs test.a[1]
* Update table SET table.value = 3 fails
* User who can create databases can modify pg_database table
* Elog() does not free all its memory(Jan)
* Disallow inherited columns with the same name as new columns
* Recover or force failure when disk space is exhausted
* Views containing aggregates sometimes fail(Jan)
* Alter TABLE ADD COLUMN does not honor DEFAULT, add CONSTRAINT
* Array index references without table name cause problems
* Views with spaces in view name fail when referenced
* Plpgsql does not handle quoted mixed-case identifiers
* Do not allow bpchar column creation without length
* INSERT INTO ... SELECT with AS columns matching result columns problem
ENHANCEMENTS
------------
* Add referential integrity
* Add OUTER joins, left and right(Thomas)
* Allow long tuples by chaining or auto-storing outside db (chaining,large objs)
* Fix memory leak for expressions?, aggregates?
Exotic features:
* Add sql3 recursive unions
* Add the concept of dataspaces
* Add replication of distributed databases
* Allow queries across multiple databases
Admin:
* Better interface for adding to pg_group
* More access control over who can create tables and access the database
* Add syslog functionality
* Allow elog() to return error codes, not just messages
* Allow international error message support and add error codes
* Generate postmaster pid file and remove flock/fcntl lock code
* Add ability to specifiy location of lock/socket files
Types:
* Add BIT, BIT VARYING
* Nchar (as distinguished from ordinary varchar),
* Domain capability
* Add STDDEV/VARIANCE() function for standard deviation computation/variance
* Allow compression of large fields or a compressed field type
* Large objects
* Fix large object mapping scheme, own typeid or reltype(Peter)
* Allow large text type to use large objects(Peter)
* Not to stuff everything as files in a single directory
* Allow pg_descriptions when creating types, tables, columns, and functions
* Add IPv6 capability to INET/CIDR types
* Make a separate SERIAL type?
* Store binary-compatible type information in the system
* Allow user to define char1 column
* Add support for & operator
Views:
* Allow DISTINCT on views
* Allow views of aggregate columns
* Allow views with subselects
* Allow subqueries in target list
* Put sort files, large objects in their on directory
* Do autocommit so always in a transaction block
* Show location of syntax error in query
* Redesign the function call interface to handle NULLs better(Jan)
* Document/trigger/rule so changes to pg_shadow create pg_pwd
* Missing optimizer selectivities for date, etc.
Indexes:
* Allow CREATE INDEX zman_index ON test (date_trunc( 'day', zman ) datetime_ops)
fails index can't store constant parameters
* Allow creation of functional indexes to use default types
* Permissions on indexes - prevent them?
* Allow SQL function indexes
* Add FILLFACTOR to index creation
Commands:
* ALTER TABLE ADD COLUMN to inherited table put column in wrong place
* Add ALTER TABLE DROP/ALTER COLUMN feature
* Allow CLUSTER on all tables at once, and improve CLUSTER
* Generate error on CREATE OPERATOR of ~~, ~ and and ~*
* Add SIMILAR TO to allow character classes, 'pg_[a-c]%'
* Auto-destroy sequence on DROP of table with SERIAL
* Allow LOCK TABLE tab1, tab2, tab3 so all tables locked in unison
* Allow INSERT/UPDATE of system-generated oid value for a row
* Allow ESCAPE '\' at the end of LIKE for ANSI compliance
* Rewrite the LIKE handling by rewriting the user string with the
supplied ESCAPE
* Move LIKE index optimization handling to the optimizer
Clients:
* Make NULL's come out at the beginning or end depending on the
ORDER BY direction
* Allow flag to control COPY input/output of NULLs
* Update reltuples from COPY command
* Allow psql \copy to allow delimiters
* Add a function to return the last inserted oid, for use in psql scripts
* Allow psql to print nulls as distinct from ""(?)
* Increase identifier length(NAMEDATALEN) if small performance hit
* Allow row re-use without vacuum, maybe?(Vadim)
* Add UNIQUE capability to non-btree indexes
* Certain indexes will not shrink, i.e. oid indexes with many inserts
* Restore unused oid's on backend exit if no one else has gotten oids
* Have UPDATE/DELETE clean out indexes
* Allow WHERE restriction on ctid
* Allow cursors to be DECLAREd/OPENed/CLOSEed outside transactions
* Allow PQrequestCancel() to terminate when in waiting-for-lock state
* Transaction log, so re-do log can be on a separate disk
* Populate backend status area and write program to dump status data
* Make oid use unsigned int more reliably, pg_atoi()
* Add PL/Perl(Mark Hollomon)
PERFORMANCE
-----------
* Allow transaction commits with rollback with no-fsync performance
* Prevent fsync in SELECT-only queries
* Use indexes in ORDER BY for restrictive data sets, min(), max()
* Pull requested data directly from indexes, bypassing heap data
* Use index to restrict rows returned by multi-key index when used with
non-consecutive keys or OR clauses, so fewer heap accesses
* Use index with constants on functions
* Allow LIMIT ability on single-table queries that have no ORDER BY to use
a matching index
* Improve LIMIT processing by using index to limit rows processed
* Cache most recent query plan(s?)
* Shared catalog cache, reduce lseek()'s by caching table size in shared area
* Allow compression of log and meta data
* Update pg_statistic table to remove operator column
* Make index creation use psort code, because it is now faster(Vadim)
* Allow char() not to use variable-sized header to reduce disk size
* Do async I/O to do better read-ahead of data
* Fix memory exhaustion when using many OR's
* Get faster regex() code from Henry Spencer <henry@zoo.utoronto.ca>
when it is available
* Use mmap() rather than SYSV shared memory(?)
* Process const = const parts of OR clause in separate pass
* Make oid use oidin/oidout not int4in/int4out in pg_type.h
* Create more system table indexes for faster cache lookups
* Improve Subplan list handling
* Allow Subplans to use efficient joins(hash, merge) with upper variable
DOCUMENTATION
-------------
* Add use of 'const' for varibles in source tree
--
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
Bruce Momjian wrote:
I have updated the TODO list, rearranging it. Here is the top of the
"Enhancements" list:* Add referential integrity
* Add OUTER joins, left and right(Thomas)
* Allow long tuples by chaining or auto-storing outside db (chaining,large objs)
* Fix memory leak for expressions?, aggregates?And the top of "Performance" is:
* Allow transaction commits with rollback with no-fsync performance
* Prevent fsync in SELECT-only queriesThis should help. Did I get all the big items just discussed?
Savepoints.
Error codes.
Vadim
I have updated the TODO list, rearranging it. Here is the top of the
"Enhancements" list:* Add referential integrity
* Add OUTER joins, left and right(Thomas)
* Allow long tuples by chaining or auto-storing outside db (chaining,large objs)
* Fix memory leak for expressions?, aggregates?And the top of "Performance" is:
* Allow transaction commits with rollback with no-fsync performance
* Prevent fsync in SELECT-only queriesThis should help. Did I get all the big items just discussed?
Savepoints.
Error codes.
I tried to pick items that users were complaining about, not items we
plan to do for 6.6.
--
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
Bruce Momjian wrote:
I have updated the TODO list, rearranging it. Here is the top of the
"Enhancements" list:* Add referential integrity
* Add OUTER joins, left and right(Thomas)
* Allow long tuples by chaining or auto-storing outside db (chaining,large objs)
* Fix memory leak for expressions?, aggregates?
How hard would it bet to separate PREPARE and EXECUTE for queries
and provide some way to pass arguments without converting them to some
ascii representation first?
The main use I need it for is storing small images in ordinary table
fields.
The mechanics should already be there as SPI uses it.
----------------
Hannu
Bruce Momjian <maillist@candle.pha.pa.us> writes:
Did I get all the big items just discussed?
Eliminating limits on textual query length.
(This is not same thing as increasing tuple size, although in practice
we'd want to do both in the same release.)
regards, tom lane
Import Notes
Reply to msg id not found: YourmessageofSun6Jun1999224320-0400199906070243.WAA19518@candle.pha.pa.us | Resolved by subject fallback
Done.
Bruce Momjian <maillist@candle.pha.pa.us> writes:
Did I get all the big items just discussed?
Eliminating limits on textual query length.
(This is not same thing as increasing tuple size, although in practice
we'd want to do both in the same release.)regards, tom lane
--
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
Did I get all the big items just discussed?
Maybe they're too big issues just to add, but when I discuss Postgresql
with people responsible for company decisions about databases they
always mention
- Scalability. This may come if PostgreSQL INC will introduce
clusterwide servers
- Security. One main point is the roll forward facility. I think all
the commercial db's has this?
- Up time. This means hot backup and no locking of the database during
vacuum.
- Up time. This means hot backup and no locking of the database during
vacuum.
If Vadim made the change to make pg_dump dump in one transaction then
PostgreSQL already has "hot backup" in 6.5. This will do a consistent
snapshot of your database as it was when pg_dump began as long as you
don't change the database layout during the dump.
Andreas
Import Notes
Resolved by subject fallback
ZEUGSWETTER Andreas IZ5 wrote:
- Up time. This means hot backup and no locking of the database during
vacuum.If Vadim made the change to make pg_dump dump in one transaction then
PostgreSQL already has "hot backup" in 6.5. This will do a consistent
snapshot of your database as it was when pg_dump began as long as you
don't change the database layout during the dump.
This is done.
Vacuum doesn't lock entire database. But it acquires access
exclusive lock over table being vacuumed and so delay all
(even SELECT) concurrent query executions. Lock released
after table vacuumed.
Vadim
At 03:44 PM 6/8/99 +0800, Vadim Mikheev wrote:
ZEUGSWETTER Andreas IZ5 wrote:
If Vadim made the change to make pg_dump dump in one transaction then
PostgreSQL already has "hot backup" in 6.5. This will do a consistent
snapshot of your database as it was when pg_dump began as long as you
don't change the database layout during the dump.
This is done.
You boys need to publicize this. This lacking has been one of the
biggest arguments against using Postgres in any environment with
24-hr access, one example being the web...
- Don Baccus, Portland OR <dhogaza@pacifier.com>
Nature photos, on-line guides, and other goodies at
http://donb.photo.net
Don Baccus wrote:
At 03:44 PM 6/8/99 +0800, Vadim Mikheev wrote:
ZEUGSWETTER Andreas IZ5 wrote:
If Vadim made the change to make pg_dump dump in one transaction then
PostgreSQL already has "hot backup" in 6.5. This will do a consistent
snapshot of your database as it was when pg_dump began as long as you
don't change the database layout during the dump.This is done.
You boys need to publicize this. This lacking has been one of the
biggest arguments against using Postgres in any environment with
24-hr access, one example being the web...
We discussed this issue recently and decided to follow this way,
so I didn't post message when pg_dump was changed, assuming
that it's known by all -:)
Or you talk that this should be mentioned in announcement/release
notes? May be... Though this is obvious feature of MVCC -
consistency read without blocking writers.
Vadim
Or you talk that this should be mentioned in
announcement/release notes?
I've added a mention of this in the release notes, and (Bruce) since
I'll be regenerating INSTALL and HISTORY it will be included in those.
I *should* be able to retrofit it into admin.ps.gz also...
- Thomas
--
Thomas Lockhart lockhart@alumni.caltech.edu
South Pasadena, California
At 10:11 PM 6/8/99 +0800, Vadim Mikheev wrote:
We discussed this issue recently and decided to follow this way,
so I didn't post message when pg_dump was changed, assuming
that it's known by all -:)
I don't mean to this group, or any of the postgres groups,
I mean to the world at large, in which Postgres has a very
negative image for web work. Consistent dumps, killing
of one very bad memory leak (and a bunch of not-so-bad
ones), and moving to mvcc from table-locking - these are
three huge improvements for people building web sites.
Folks outside the normal Postgres community deserve to
know this.
And the latest download executes my "group by" clauses rather
than killing the backend, as I found out last night. I've
just sped up a page that returns a bar graph of monthly
data by an order of magnitude, woo-hoo! Before I was
forced to do a separate select for each month (against
about 100,000 records, boo-hiss), now one nice select
grouping data by month just like real databases let me
do, I'm happy!
- Don Baccus, Portland OR <dhogaza@pacifier.com>
Nature photos, on-line guides, and other goodies at
http://donb.photo.net
- Up time. This means hot backup and no locking of the database during
vacuum.If Vadim made the change to make pg_dump dump in one transaction then
PostgreSQL already has "hot backup" in 6.5. This will do a consistent
snapshot of your database as it was when pg_dump began as long as you
don't change the database layout during the dump.
Excellent point.
--
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
At 10:11 PM 6/8/99 +0800, Vadim Mikheev wrote:
We discussed this issue recently and decided to follow this way,
so I didn't post message when pg_dump was changed, assuming
that it's known by all -:)I don't mean to this group, or any of the postgres groups,
I mean to the world at large, in which Postgres has a very
negative image for web work. Consistent dumps, killing
of one very bad memory leak (and a bunch of not-so-bad
ones), and moving to mvcc from table-locking - these are
three huge improvements for people building web sites.
Folks outside the normal Postgres community deserve to
know this.And the latest download executes my "group by" clauses rather
than killing the backend, as I found out last night. I've
just sped up a page that returns a bar graph of monthly
data by an order of magnitude, woo-hoo! Before I was
forced to do a separate select for each month (against
about 100,000 records, boo-hiss), now one nice select
grouping data by month just like real databases let me
do, I'm happy!
We really don't have access to web admin channels except through our
mailing list and software lists. You need to get the word out. We
addressed these issues escecially for web/high traffic users.
--
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
Or you talk that this should be mentioned in
announcement/release notes?I've added a mention of this in the release notes, and (Bruce) since
I'll be regenerating INSTALL and HISTORY it will be included in those.
I *should* be able to retrofit it into admin.ps.gz also...
Added to release notes:
Another big benefit of MVCC is that <application>pg_dump</application>
can now generate consistent backups of live, active databases, without
blocking active transactions.
Good idea to add this. I also added to the Enhancements list:
pg_dump now can generate consistent snapshots on active databases(Vadim)
--
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
At 12:25 PM 6/8/99 -0400, Bruce Momjian wrote:
We really don't have access to web admin channels except through our
mailing list and software lists. You need to get the word out. We
addressed these issues escecially for web/high traffic users.
I have been, quietly, to people I know. I gave up on 6.4.2 for my
particular use and had told folks that, and have now told the same
suite of folks that 6.5 appears to be a vast improvement for this
environment, at least for modest web/db projects. Postgres still
doesn't have anywhere near the scalability of, say, Oracle and I'm
not certain that should be the goal. It's far simpler to administer
and install largely for this very reason...and that's a very good
thing for folks wanting to do modest sites.
Any graphics designers out there? How about a small "Powered
by Postgres" GIF with a snazzy, attractive look? I've come
up with the phrase, but my artistic skills are limited to
photography, I'm afraid!
I'd certainly use such a graphic to decorate my pages if it
were available...
- Don Baccus, Portland OR <dhogaza@pacifier.com>
Nature photos, on-line guides, and other goodies at
http://donb.photo.net
Don Baccus wrote:
Any graphics designers out there? How about a small "Powered
by Postgres" GIF with a snazzy, attractive look? I've come
up with the phrase, but my artistic skills are limited to
photography, I'm afraid!I'd certainly use such a graphic to decorate my pages if it
were available...
I posted one below a days ago... Any chance to see all such
things somewhere in ftp/www postgresql.org servers?
Vadim
P.S. Created by Michael Ivanov <mike@if-site.com>
Attachments:
pgsql_emp.gifimage/gif; name=pgsql_emp.gifDownload
GIF89aX � ��|��5��G��I��\�j�(
��L��0�����x��)�(�f%����I]>$���P�����3�y6���.��S��~^&�����0�Z#�7664rrt��J����h p4�\(v>/s*
��1�8�yH�{A�����x-� W
qVVT�g%�Y�[&��g��b��)t3U4��/��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:��:!�NETSCAPE2.0 !�Made with GIMP !�
% , X ��������������'�'����������0'0�������&&��&��� � '�&��� �� �' ���������������������������������00����������������'��+��+(x�4 �<e@�q�W�����N�*h���
h�
|��u�,cH�"����= @D@�*���Q�����T!5�TE�����R��":��2j���@
2�`C�5XP��U�&``8!c]Q]CM`��1���|5^ ���)�.p1��
Z!����������-�&@�x�����p1\�x���8PrbU4 ��u#� ���Z@���(0����(<`~��6��>����s
9VmW4��e������0����4������W�]��&��� ,��
�4(�g���F_�G� E�5@`@���`�1x "@�H@�A2�P"7|��,�H�F&@P�[1 ��^�"�X
� �������%�DA�'�h��tv�R#�h >T2"t A�P9��E�� � l�A:6`p�e��
'V��|�p�Az�J�Ea &�PA�"2��28`�(p���@A�8�0"@�A4� A|����`C�<���x"�l0� �`��eB�t �|�B�B�)�@0�D�h�I���jg�$�i�(���+�17|��h����$ �
0� ��"7t�[��h��:���p�-7��A 0�����k���S�x`�7��� �06�;�����v0@��� 5�R�k�p� $P���� � 0�����@��<@A��X��!0D ���0�
g ��WW@@
u
�b�lP��Yn
�R��l�6��(!���!�vH<4 �
L��,���0�p�r�����B
X�v�`Cl���=V��,tv�
���)��8��@����Y��v�`A
��@T`2����������
?���� �����~�+��p�
h`�,?� s�G�TI ��,p�H�������~`3$ ?��@�)\�j?h�k�D�R���h,��`�S���$x��[ai6���2 �G�`x@�����/���`#A��4C�@�� h@�P��/�HAH�
��)����
N>�.�AA�p� F&1 I` x� D��I��&���&�YL '�A�a��g���I �������@Q4�E����>;H���`��@Jd �h\
���nz����8�I�r�s��fj��� ��A ��w ���f���}���9�'<��������A7 jOo�$ �B�, ��hE��J5� d�vv@�(E ��n��Ck(0���vs�!]@IS�NAtsW���K!R�FT�;��Q1JS�~���@Gz�S�F4�;jJ�S�t�4�i @��t�I�(Qa:���t�TMi �RpM�+] �P����)�]-Z��t��*L
V D�.�jFy����U)=!O�J��<e*[�J�A�3��d�@s�N������a�!�w�����-?AJ����4=�p�K���3 !�
, X ��������������'