Re: pgsql/src/test/regress/expected (plpgsql.out inet.out foreign_key.out errors.out) - Mailing list pgsql-committers

From Thomas Lockhart
Subject Re: pgsql/src/test/regress/expected (plpgsql.out inet.out foreign_key.out errors.out)
Date
Msg-id 39F3E076.F793977A@alumni.caltech.edu
Whole thread Raw
In response to pgsql/src/test/regress/expected (plpgsql.out inet.out foreign_key.out errors.out)  (Tom Lane <tgl@postgresql.org>)
Responses Re: pgsql/src/test/regress/expected (plpgsql.out inet.out foreign_key.out errors.out)  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-committers
> Modified Files:
...
> Some small polishing of Mark Hollomon's cleanup of DROP command: might
> as well allow DROP multiple INDEX, RULE, TYPE as well.  Add missing
> CommandCounterIncrement to DROP loop, which could cause trouble otherwise
> with multiple DROP of items affecting same catalog entries.  Try to
> bring a little consistency to various error messages using 'does not exist',
> 'nonexistent', etc --- I standardized on 'does not exist' since that's
> what the vast majority of the existing uses seem to be.

Good idea(s). Thanks for cleaning up the error messages...

                    - Thomas

pgsql-committers by date:

Previous
From: "Vadim B. Mikheev - CVS"
Date:
Subject: pgsql/src/include/utils (relcache.h)
Next
From: Bruce Momjian
Date:
Subject: Re: pgsql/src/test/regress/expected (plpgsql.out inet.out foreign_key.out errors.out)