Hi All,

I have a question or two about the call report maximum query length
flag (-q flag)...

1) What is the absolute maximum for the maximum query size?

2) Is there any performance issues when setting this at a high value
when the actual query in the report is small?

The manual that I found states that it defaults to 2048, but does not
say what the limit is...

Just wondering why it was created in the first place? We have a central
location for most of our report calls and I am thinking of overriding
the passed-in value for the maxquery length to something like 15000.
Anyone done something like this before? Is there anything I need to
watch for?

Regards,
Andrew.

Andrew wrote:

I'm not aware of one. If there is one, it's big.

I really, really doubt it.

I suspect it is a fossil dating back to the very early days, when we ran
Ingres on VAX 11/750s with as much as 4Mb of RAM, and every byte
was precious.

Not recently. The last time I ran into problems with the size of a query
was several decades ago.

Sabre-toothed tigers? :-)

--
Roy

UK Ingres User Association Conference 2009 will be on Tuesday June 9, 2009
Go to http://www.iua.org.uk/join to get on the mailing list.

Thanks Roy.

Sorry, no witty response (too tired - work/bills/wife/kids...), but
willing to proxy it to someone else.


Roy Hann wrote:

On Mar 2, 2009, at 11:23 PM, Andrew wrote:

There isn't any program-enforced upper limit. You can make it bigger
until you run out of memory.

No, other than indirect issues caused by memory pressure if you use
an insanely large value.

The current default (since 1991, apparently) is 5000.

It would probably make sense to raise this default by at least a factor
of 10. It's a trivial change (MQ_DFLT in front/report/hdr/rcons.h).
For extra credit, someone could trash the need for -q entirely, and make
the query buffer expand as needed. That might take as long as an
hour or
two. (Hint: report/report/rqurset.c)


I'm quite sure that Roy's answer is correct, that it is a fossil from
the olden days.

Karl

I just love the way Karl made those code changes that sound so easy!

Other than sabre-toothed tigers...what else is there to worry about!

Marty

-----Original Message-----
From: info-ingres-bounces (AT) kettleriver...ting (DOT) com
[mailto:info-ingres-bounces (AT) kettleriverconsulting (DOT) com] On Behalf Of Karl
& Betty Schendel
Sent: 03 March 2009 15:38
To: Ingres and related product discussion forum
Subject: Re: [Info-Ingres] Report Writer (-q flag)


On Mar 2, 2009, at 11:23 PM, Andrew wrote:

There isn't any program-enforced upper limit. You can make it bigger
until you run out of memory.

No, other than indirect issues caused by memory pressure if you use
an insanely large value.

The current default (since 1991, apparently) is 5000.

It would probably make sense to raise this default by at least a factor
of 10. It's a trivial change (MQ_DFLT in front/report/hdr/rcons.h).
For extra credit, someone could trash the need for -q entirely, and make
the query buffer expand as needed. That might take as long as an
hour or
two. (Hint: report/report/rqurset.c)


I'm quite sure that Roy's answer is correct, that it is a fossil from
the olden days.

Karl

_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://www.kettleriverconsulting.com...fo/info-ingres