From: | Goran Thyni <goran(at)kirra(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Zsolt Varga <redax(at)agria(dot)hu>, PostgreSQL hackers list <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] still Query Limits to 8K ? |
Date: | 1998-11-21 11:14:22 |
Message-ID: | 3656A08E.23F24EB9@kirra.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> One thing I do not know is whether we'd start to run into any hard-wired
> limits in the parser/planner/executor with very large (complex) queries
> ... Thomas, would the parser go down if you handed it a SELECT with a
> few thousand OR clauses?
Yep, I know one:
include/utils/elog.h:32:#define ELOG_MAXLEN 4096
I made a patch before 6.4, which was backed out because
I used vsnprintf which wasn't available everywhere.
This is still to short, suggests we do this for 6.4.1:
#define ELOG_MAXLEN 8192
And use my patch (with fixes) for 6.5.
regards,
--
-----------------
Göran Thyni
http://kirra.net/
From | Date | Subject | |
---|---|---|---|
Next Message | Peter T Mount | 1998-11-21 12:29:35 | Re: [HACKERS] Solaris 7 |
Previous Message | Oliver Elphick | 1998-11-20 23:30:29 | pg_dump bug - problems along the way |