From: Bruce Momjian <maillist@candle.pha.pa.us>
To: jwieck@debis.com
Cc: hackers@postgreSQL.org
Subject: Re: [HACKERS] Open 6.4 items
Date: Fri, 2 Oct 1998 10:47:16 -0400 (EDT)
Message-ID: <199810021447.KAA05651@candle.pha.pa.us> (raw)
In-Reply-To: <m0zP2Kn-000EBQC@orion.SAPserv.Hamburg.dsh.de>
> >
> > We still have some release-stoppper items on this list.
> >
> > I need to integrate the cidr type into the system.
> >
> > ---------------------------------------------------------------------------
> >
> > Possible additions
> > ------------------
> > cidr/IP address type(Tom Helbekkmo)
> > rewrite system(Jan)
>
> I'm still waiting for 2 patches I sent to you to get applied.
> Subjects where:
>
> rewrite rules patch
>
> Fix for pg_views/pg_rules and new system views
>
> Do you need them again?
I am afraid I do. I don't have them.
>
> Still must tidy up the rewrite stuff and add the checks for
> rules on select. But I would like the two patches applied
> first to get in sync with CVS.
>
> > notify fixes(Tom)
> >
> > Serious Bugs
> > ------------
> > change pg args for platforms that don't support argv changes
> > (setproctitle()?, sendmail hack?)
> > have psql dump out rules text with new function
>
> This requires the second patch, because it covers subselect
> backparsing for pg_get_ruledef.
>
> > man pages/sgml synchronization
> > generate html/postscript documentation
> > generate postmaster pid file and remove flock/fcntl lock code
> > 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
>
> Will take a look at it.
>
> > handle oid's on views by either disallowing it or meaningful results
> > CREATE INDEX i_test ON pg_class (upper(relname)) fails
>
> Don't functional indices need an operator class too?
yes.
--
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: maillist@candle.pha.pa.us, jwieck@debis.com, hackers@postgreSQL.org
Subject: Re: [HACKERS] Open 6.4 items
In-Reply-To: <199810021447.KAA05651@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox