As this thread reports (some sever messages are in Chinese):
http://archives.postgresql.org/pgsql-bugs/2005-07/msg00247.php
a SQL grammar error could crash the error stack.
My explaination is that select; incurs a parse error and this error
message is
supposed to be translated into your
Qingqing Zhou [EMAIL PROTECTED] writes:
As this thread reports (some sever messages are in Chinese):
http://archives.postgresql.org/pgsql-bugs/2005-07/msg00247.php
a SQL grammar error could crash the error stack.
Hmm, I thought we had fixed that years ago.
To fix this, we just change
I just realised this mail didn't go through. Probably because it was too
large for -hackers. So: repost to -patches. Sorry about that. If it's a
duplicate, even more sorry, but I couldn't find it in the archives.
(This may explain that nobody answered me :P)
//Magnus
-Original
Tom Lane [EMAIL PROTECTED] writes
This is a really ugly solution ... and I don't think it solves the
general problem anyway, since this isn't the only possible error message.
Yeah, it is not a very clean solution. Do you mean the general problem is
prevent recursive error reporting because
Michael Fuhr wrote:
On Thu, Jul 28, 2005 at 03:56:14PM +0100, Sean Burlington wrote:
Michael Fuhr wrote:
On Thu, Jul 28, 2005 at 12:48:35PM +0100, Sean Burlington wrote:
Description:inheritance removes permissions from the parent table
I think a more accurate description would be
