Thread: Open 6.4 Items

Possible additions
------------------
cidr/IP address type(Tom Helbekkmo)
rewrite system(Jan)
foreign key?(Vadim)

Serious Bugs
------------
change pg args for platforms that don't support argv changes
    (setproctitle()?, sendmail hack?)
pg_user dumps core on some platforms
have psql dump out rules text with new function
man pages/sgml synchronization
generate html/postscript documentation
generate postmaster pid file and remove flock/fcntl lock code
regproc dumps name_oid, which fails on CREATE TYPE
CREATE TABLE test (x text, s serial) fails if no database creation permission
SELECT * FROM pg_rules WHERE pg_rules.oid = pg_class.oid crashes
handle oid's on views by either disallowing it or meaningful results
certain AND/OR WHERE clauses crash backend
select not bool_field from t1 crashes
CREATE TABLE bar (id serial, name varchar(32)) fails

New Bugs
--------
cnf-ify still can exhaust memory, make SET KSQO more generic
permissions on indexes:  what do they do?  should it be prevented?
remove PARSEDEBUG defines if not longer needed
low level locking - work-in-progress for 6.5
improve reporting of syntax errors by showing location of error in query
use index with constants on functions
allow chaining of pages to allow >8k tuples
allow multiple generic operators in expressions without the use of parentheses
document/trigger/rule so changes to pg_shadow create pg_pwd
large objects orphanage
improve group handling
no min/max for oid type

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
http://www.op.net/~candle              |  (610) 353-9879(w)
  +  If your life is a hard drive,     |  (610) 853-3000(h)
  +  Christ can be your backup.        |

Bruce Momjian wrote:
> allow chaining of pages to allow >8k tuples

How transparent is this going to be?  Am I going to need to specify that a
table needs to be 'chainable', or is it just going to do it when I create
tables that can have records containing >8k of data?  I have several databases
that I would like to move over to a postgres backend from 4th Dimension, but
many tables have the potential of creating tuples greater than 8k.

Thanks,
Nick

> Bruce Momjian wrote:
> > allow chaining of pages to allow >8k tuples
>
> How transparent is this going to be?  Am I going to need to specify that a
> table needs to be 'chainable', or is it just going to do it when I create
> tables that can have records containing >8k of data?  I have several databases
> that I would like to move over to a postgres backend from 4th Dimension, but
> many tables have the potential of creating tuples greater than 8k.
>
> Thanks,
> Nick
>

Automatically.  We have had no one offer to do it, yet.

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
http://www.op.net/~candle              |  (610) 353-9879(w)
  +  If your life is a hard drive,     |  (610) 853-3000(h)
  +  Christ can be your backup.        |

Bruce Momjian wrote:
>
> > Bruce Momjian wrote:
> > > allow chaining of pages to allow >8k tuples
> >
> > How transparent is this going to be?  Am I going to need to specify that a
> > table needs to be 'chainable', or is it just going to do it when I create
> > tables that can have records containing >8k of data?  I have several databases
> > that I would like to move over to a postgres backend from 4th Dimension, but
> > many tables have the potential of creating tuples greater than 8k.
> >
> > Thanks,
> > Nick
> >
>
> Automatically.  We have had no one offer to do it, yet.

Ahh, well...bummer, then.. ;-)

Nick