Re: About dependency reports in DROP RESTRICT - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: About dependency reports in DROP RESTRICT
Date
Msg-id 20080605231837.GV16502@alvh.no-ip.org
Whole thread Raw
In response to About dependency reports in DROP RESTRICT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:

> So what I'd like to do about it is just use the CASCADE style all the
> time.  Thoughts?

It is loss of functionality, but I very much doubt anyone is depending
on it -- it's way too elaborate.  +1 on doing the simpler report if it's
too expensive to build the full report.

> BTW, it would now be possible to do something like what the shdepend
> code does, and stuff all these reports into the DETAIL field of a
> single message, instead of emitting them as separate notices.
> Any feelings pro or con about that?

I think it makes more sense to do it that way (considering that they're
really part of the single error message, not independent reports), but
there's the problem that the error report gets too long.  So we would
have to send a truncated report to the client and the full report to the
log only.  Would people be upset at that?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: About dependency reports in DROP RESTRICT
Next
From: Gregory Stark
Date:
Subject: Re: About dependency reports in DROP RESTRICT