Re: Fixing domain input - Mailing list pgsql-hackers

From Michael Glaesemann
Subject Re: Fixing domain input
Date
Msg-id 0B447D7A-E810-42AD-AA63-AABA91A5DCE5@myrealbox.com
Whole thread Raw
In response to Re: Fixing domain input  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fixing domain input  (Christopher Kings-Lynne <chris.kings-lynne@calorieking.com>)
Re: Fixing domain input  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Apr 4, 2006, at 10:39 , Tom Lane wrote:

> So there's no additional risk --- in fact, arguably having such a
> function crash during normal input of NULL would be a Good Thing,
> because it would make it far more likely that the mistake would get
> noticed and fixed before someone used it as a form of DOS attack.

Granted, finding an error earlier than later is a Good Thing, but an  
Even Better Thing would be to prevent crashing the backend, and  
afaics (as far as that is) the change you propose doesn't hurt  
anything. Do you see any way to do that?

I'm glad to see work being done on domains. I'm definitely learning  
from the discussion.

Michael Glaesemann
grzm myrealbox com





pgsql-hackers by date:

Previous
From: "Peter Brant"
Date:
Subject: Stats collection on Windows
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Fixing domain input