04-01-2014
There may be repeated rogue queries that are trying to return vast amounts of data. If the user is disconnected/timed out/gets bored, they may well re-issue. I would consider reading the application logs to check that the queries are indeed going to return suitable data volumes.
This was learned from prolonged painful experience eventually leading to better validation and sanity checking on the application server before the query was executed.
Robin
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello, everyone:
i encounter a problem these days , pls help me ,thanks in advance.
my env:
machine: ES40 A ES40 B
os: true64 Unix 4.0f
note: src.tar 8M network card speed 100M
my problem:
... (3 Replies)
Discussion started by: q30
3 Replies
2. AIX
Hi,
I am trying to send oracle archives over WAN and it is taking hell a lot of time. To reduce the time, I tried to gzip the files and send over to the other side. That seems to reduce the time. Does anybody have experienced this kind of problem and any possible ways to reduce the time.
... (1 Reply)
Discussion started by: giribt
1 Replies
3. Solaris
At work, I'm in a Solaris environment working with csh, and $PATH is populated with anywhere between 10 and 20 entries.
Last week, every command I issued (even "ls") took several seconds, if not an entire minute, to run. Once I moved "/home/sybase/bin" to the end of $PATH, certain commands... (2 Replies)
Discussion started by: acheong87
2 Replies
4. Red Hat
hey guys,
We have two Sun x2100 servers running RHEL5 in a test environment. Both servers are fresh OS installs and hooked up to the same network switch.
When ssh'ing to one server, there is a significant delay, while ssh'ing to the other server, the connection is almost instant. We are... (2 Replies)
Discussion started by: amheck
2 Replies
5. BSD
hi
howto restart the network with a wireless interface including wpa_supplicant on freeBSD 7.2 without reboot? (3 Replies)
Discussion started by: ccc
3 Replies
6. AIX
Hi All,
Please let me know the command to restart the network interface and enable it on boot in AIX, similar to /etc/init.d/network restart in Redhat.
Thanks,
Sunil.K
please watch out to post in the right subforum! (9 Replies)
Discussion started by: sunilrk07
9 Replies
7. UNIX for Advanced & Expert Users
Hi Guys,
I've inherited a mess of an infrastructure in my new job, there hasn't been a sys admin in post for about a year, so things are falling apart. The first thing to break after I started was the printer server. I have it working again, and people can print, however it's very slow, slower... (0 Replies)
Discussion started by: rudigarude
0 Replies
8. Solaris
I have identical M5000 machines that are needing to transfer very large amounts of data between them. These are fully loaded machines, and I've already checked IO, memory usage, etc... I get poor network performance even when the machines are idle or copying via loopback. The 10 GB NICs are... (7 Replies)
Discussion started by: christr
7 Replies
9. AIX
Hello everyone,
I've been a life long Unix/Linux user but I'll be the first to admit I have little specific AIX knowledge at this point and I've inherited these systems for better or worse so please forgive if I ask something in the wrong context. And yes, I've searched google for 3 days now :)... (3 Replies)
Discussion started by: BDMcGrew
3 Replies
10. Debian
Hello,
I would like to do follow steps.
Set a static IP-Adress on eth0 (For Testing)
Set DHCP on eth0
All steps should be done without a single reboot.
/etc/network/interfaces
iface eth0 inet static
address 192.0.2.7/24
gateway 192.0.2.254How do i perform... (3 Replies)
Discussion started by: int3g3r
3 Replies
LEARN ABOUT REDHAT
prepare
PREPARE(7) SQL Commands PREPARE(7)
NAME
PREPARE - create a prepared query
SYNOPSIS
PREPARE plan_name [ (datatype [, ...] ) ] AS query
INPUTS
plan_name
An arbitrary name given to this particular prepared query. It must be unique within a single session, and is used to execute or
remove a previously prepared query.
datatype
The data-type of a parameter to the prepared query. To refer to the parameters in the prepared query itself, use $1, $2, etc.
OUTPUTS
PREPARE
The query has been prepared successfully.
DESCRIPTION
PREPARE creates a prepared query. A prepared query is a server-side object that can be used to optimize performance. When the PREPARE
statement is executed, the specified query is parsed, rewritten, and planned. When a subsequent EXECUTE statement is issued, the prepared
query need only be executed. Thus, the parsing, rewriting, and planning stages are only performed once, instead of every time the query is
executed.
Prepared queries can take parameters: values that are substituted into the query when it is executed. To specify the parameters to a pre-
pared query, include a list of data-types with the PREPARE statement. In the query itself, you can refer to the parameters by position
using $1, $2, etc. When executing the query, specify the actual values for these parameters in the EXECUTE statement -- refer to EXECUTE
[execute(7)] for more information.
Prepared queries are stored locally (in the current backend), and only exist for the duration of the current database session. When the
client exits, the prepared query is forgotten, and so it must be re-created before being used again. This also means that a single prepared
query cannot be used by multiple simultaneous database clients; however, each client can create their own prepared query to use.
Prepared queries have the largest performance advantage when a single backend is being used to execute a large number of similar queries.
The performance difference will be particularly significant if the queries are complex to plan or rewrite. For example, if the query
involves a join of many tables or requires the application of several rules. If the query is relatively simple to plan and rewrite but rel-
atively expensive to execute, the performance advantage of prepared queries will be less noticeable.
NOTES
In some situations, the query plan produced by PostgreSQL for a prepared query may be inferior to the plan produced if the query were sub-
mitted and executed normally. This is because when the query is planned (and the optimizer attempts to determine the optimal query plan),
the actual values of any parameters specified in the query are unavailable. PostgreSQL collects statistics on the distribution of data in
the table, and can use constant values in a query to make guesses about the likely result of executing the query. Since this data is
unavailable when planning prepared queries with parameters, the chosen plan may be sub-optimal.
For more information on query planning and the statistics collected by PostgreSQL for query optimization purposes, see the ANALYZE [ana-
lyze(7)] documentation.
COMPATIBILITY
SQL92
SQL92 includes a PREPARE statement, but it is only for use in embedded SQL clients. The PREPARE statement implemented by PostgreSQL also
uses a somewhat different syntax.
SQL - Language Statements 2002-11-22 PREPARE(7)