Re: [HACKERS] how to deal with sparse/to-be populated tables

* Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> [000203 21:34] wrote:
> > -----Original Message-----
> > From: owner-pgsql-hackers(at)postgreSQL(dot)org
> > [mailto:owner-pgsql-hackers(at)postgreSQL(dot)org]On Behalf Of Tom Lane
> >
> > Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> writes:
> > > Hmm. Doesn't PostgreSQL have a big list of error codes? I don't think
> > > it does, I've never seen one. There should be a way to get error
> > > codes without comparing strings. Should this be on the TODO?
> >
> > It doesn't, there should, and it already is ;-)
> >
>
> Doens't the following TODO imply it ?
>
> * Allow elog() to return error codes, not just messages
>
> Many people have complained about it.
> However,it seems not effective without a functionality of statement
> level rollback. AFAIK,Vadim has planed it together with savepoint
> functionality.

It would help, but it wouldn't be avoid the double searches I seem
to need to do to maintain a unique index.

--
-Alfred Perlstein - [bright(at)wintelcom(dot)net|alfred(at)freebsd(dot)org]