From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | Denis Afonin <vadm(at)itkm(dot)ru>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4680: Server crashed if using wrong (mismatch) conversion functions |
Date: | 2009-02-27 15:31:32 |
Message-ID: | 18983.1235748692@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> I think we should instead try to break the PANIC cycle. If we exceed
> ERRORDATA_STACK_SIZE, and we're already PANICing, we should just die
> immediately instead of throwing another PANIC about exceeding the stack
> size. The attached patch does that.
I don't think that's an improvement.
I'm not sure exactly why the previous fix for this type of problem
failed to cover this case --- did you identify why?
> However, a more serious issue is that a regular user can do that and
> bring down the whole system. I suggest that we make "CREATE [DEFAULT]
> CONVERSION" to call the conversion function with a empty string, to
> check that it is in fact capable of doing the conversion.
That part seems like a good idea, now that the conversion functions
throw errors (rather than Asserts) for wrong calls.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2009-02-27 15:51:01 | Re: BUG #4680: Server crashed if using wrong (mismatch) conversion functions |
Previous Message | Heikki Linnakangas | 2009-02-27 15:10:45 | Re: BUG #4679: invalid UTF-8 byte sequence detected near byte 0xa3 + postgresql |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-02-27 15:44:01 | Re: Immediate shutdown and system(3) |
Previous Message | Tom Lane | 2009-02-27 15:25:48 | Re: Error codes for LIMIT and OFFSET |