From: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Parser emits mysterious error message for very long tokens |
Date: | 2015-09-14 07:46:59 |
Message-ID: | 20150914.164659.97530875.horiguchi.kyotaro@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello, thank you for the opinion.
At Fri, 11 Sep 2015 09:31:30 -0400, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote in <884(dot)1441978290(at)sss(dot)pgh(dot)pa(dot)us>
> Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> writes:
> > Hello, this is a problem on an extreme situation.
> > When parser encounters very long tokens, it returns an error
> > message which should be mysterious for users.
>
> >> $ perl -e "print \"select '\" . \"x\"x(512*1024*1024) . \"'\"" | psql postgres
> >> ERROR: invalid memory alloc request size 1073741824
>
> I can't get terribly excited about that, because there is not that
> much daylight between there and where the query fails because the
> entire input string exceeds 1GB. Moreover, anyone who tries working
> with literals in this size range will soon learn not to ;-). So
> it seems quite an artificial example to me ...
>
> regards, tom lane
Yes, so 'an extreme situation'. I wanted to know what to think
about this kind of situation.
Thanks for the comment, I'm confident that fixing it and the
similars in clean way should be too-much for the necessity.
regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2015-09-14 08:00:24 | Re: PATCH: index-only scans with partial indexes |
Previous Message | Kyotaro HORIGUCHI | 2015-09-14 07:35:50 | Re: PATCH: index-only scans with partial indexes |