Skip site navigation (1) Skip section navigation (2)

Re: Open 7.1 items

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Open 7.1 items
Date: 2001-01-26 04:09:11
Message-ID: 3A70F867.13C754CB@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-jdbc
Peter Eisentraut wrote:
> 
> Bruce Momjian writes:
> 
> > FOREIGN KEY INSERT & UPDATE/DELETE in transaction "change violation"
> 
> You're certainly not going to want to fix this now after having stared at
> it for a year?  It's not trivial.
> 

What does this item mean ?

> > Usernames limited in length
> 
> Yeah, they are. ;-)
> 
> If this is referring to pg_passwd, I just had a closer look and it's
> really a desaster.  Both password and username as well as line length and
> file length (in lines) have arbitrary limits, sometimes not even
> consistent ones.  To fix this to a point where one is confident that
> everything works one essentially would have to rewrite the whole thing.
> 
> > Does pg_dump preserve COMMENTs?
> 
> Sure
> 
> > Fix ipcclean on Linux
> 
> Consider it done.
> 
> > Merge global and template BKI files?
> 
> Not this release.
> 
> --
> Peter Eisentraut      peter_e(at)gmx(dot)net       http://yi.org/peter-e/

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2001-01-26 04:15:09
Subject: Re: BETWEEN patch
Previous:From: Tom LaneDate: 2001-01-26 03:13:29
Subject: Re: beta3 Solaris 7 (SPARC) port report [ Was: Looking for . . . ]

pgsql-jdbc by date

Next:From: Hiroshi InoueDate: 2001-01-26 04:18:15
Subject: Re: Open 7.1 items
Previous:From: Ron SofrinDate: 2001-01-26 03:57:32
Subject: Invoking sql functions through jdbc

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group