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

Re: Open 7.1 items

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: 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-25 16:37:08
Message-ID: Pine.LNX.4.30.0101251730390.1136-100000@peter.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-jdbc
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.

> 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?


> Fix ipcclean on Linux

Consider it done.

> Merge global and template BKI files?

Not this release.

Peter Eisentraut      peter_e(at)gmx(dot)net

In response to


pgsql-hackers by date

Next:From: Peter EisentrautDate: 2001-01-25 16:49:51
Subject: RE: Permissions on CHECKPOINT
Previous:From: Oleg BartunovDate: 2001-01-25 16:31:56
Subject: new version of contrib-intarray

pgsql-jdbc by date

Next:From: Peter T MountDate: 2001-01-25 17:07:53
Subject: Re: Re: [INTERFACES] BIT type still not working
Previous:From: Peter T MountDate: 2001-01-25 13:38:06
Subject: Re: JDBC buggy in 7.1beta3

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