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

Re: Error codes revisited

From: greg(at)turnstep(dot)com
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Error codes revisited
Date: 2003-03-05 14:51:17
Message-ID: cc265fea25d053ab227eeb2fbad5524a@biglumber.com (view raw or flat)
Thread:
Lists: pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> The *last* thing we need is a half-baked stopgap solution that we'll
> have to be backwards-compatible with forevermore.  Fix it right or
> don't do it at all, is MHO.

I agree.

> There is still barely enough time to do the long-threatened protocol
> revision for 7.4, if we suck it up and get started on that now.  I've
> been avoiding the issue myself, because it seems generally boring and
> thankless work, but maybe it's time to face up to it?

Definitely. Sure seems to be a lot involved, looking at the TODO page. 
Which brings up another question - if a protocol change doesn't warrant 
a bump to 8.0, what does? :)

- --
Greg Sabino Mullane  greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200303040645

-----BEGIN PGP SIGNATURE-----
Comment: http://www.turnstep.com/pgp.html

iD8DBQE+ZC1LvJuQZxSWSsgRAkJLAKDUE54ZELrPc4ASqEtwUCk7CYJH/ACfZ7nQ
bLRqMde1T9MDjzmejF+PBis=
=Plww
-----END PGP SIGNATURE-----



In response to

pgsql-hackers by date

Next:From: Merlin MoncureDate: 2003-03-05 15:18:32
Subject: Re: XML ouput for psql
Previous:From: Eric D NielsenDate: 2003-03-05 14:48:48
Subject: Re: Updateable views...

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