memory usage.
--
Peter Haworth [EMAIL PROTECTED]
Q: Why do ducks have flat feet? A: To stamp out forest fires.
Q: Why do elephants have flat feet? A: To stamp out flaming ducks
-- UNIX fortune
---(end of broadcast
On Sat, 11 Dec 2004 10:44:59 -0600, Wes wrote:
On 12/9/04 9:23 AM, Peter Haworth [EMAIL PROTECTED] wrote:
It runs RHEL ES v3, kernel 2.4.21-20.ELsmp
It's generally a very stable box which runs a number of postgresql
instances. But last night we hit very high low averages - 10+, vs
is this, which we are looking into:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132155
It would be good to eliminate all possible causes, though.
--
Peter Haworth [EMAIL PROTECTED]
Of course, if you were to print(1..Inf), you'd have plenty of time to go and
get a cup of coffee
we really need immediately.
--
Peter Haworth [EMAIL PROTECTED]
There are two ways of constructing a software design. One way is to make
it so simple that there are obviously no deficiencies and the other is to
make it so complicated that there are no obvious deficiencies
Tom Lane writes:
It would make sense to offer a strict mode in which the date order
has to be what DateStyle suggests.
Something like this?
set datestyle='iso,strict';
I could live with that.
--
Peter Haworth [EMAIL PROTECTED]
ADD Lesson #4: In a Crisis, everyones' alignment
going to change), you can simply say:
if($cust_data-{hold})
However, if you want cross-database portability (and protection from
DBD::Pg's behaviour changing), you have to do this:
if($cust_data-{hold}=~/[t1]/)
--
Peter Haworth [EMAIL PROTECTED]
perl -e '$|=s\rJust another Perl
,$company)=map $dbh-quote($_),
@env_array{qw(User UserEmail ServiceLevel AccountManager Company)};
$dbh-do(qq(
insert into env_info
(username,useremail,servicelevel,accountmanager,company)
values($uname,$email,$level,$mgr,$company)
));
--
Peter Haworth [EMAIL
On Wed, 30 May 2001 12:54:17 -0400, [EMAIL PROTECTED] wrote:
On Wed, May 30, 2001 at 04:02:51PM +0100, Peter Haworth wrote:
On Wed, 30 May 2001 08:07:11 -0400, [EMAIL PROTECTED] wrote:
The new behaviour is mre correct.
Why? The old behavior is better. Less coding.
It's also less
statement handles which all rows had been fetched from.
The new behaviour is mre correct.
--
Peter Haworth [EMAIL PROTECTED]
I'm just a mere programmer
-- James Counihan
---(end of broadcast)---
TIP 1: subscribe
error_msg end[-1] == '\n'; --end);
+
src = error_msg;
dst = err;
/* copy error message without trailing newlines */
-while (*dst != '\0' *dst != '\n') {
+while (src end){
*dst++ = *src++;
}
*dst = '\0';
--
Peter Haworth [EMAIL
the connection to the backend, so further processing is
impossible. Terminating.
That's obviously too sneaky.
--
Peter Haworth [EMAIL PROTECTED]
Anything that can go wrong, will go wr
On Wed, 15 Nov 2000 11:19:40 -0500, Tom Lane said:
Peter Haworth [EMAIL PROTECTED] writes:
I'm having trouble getting Postgres 6.5.3 to do what I want. The
problem seems to be fixed in version 7, but I could really do with a
workaround for 6.5.3, since I'm stuck with that for the time
-fetchrow_hashref){
push @taghash,{%$row};
}
Or, better yet:
$taghash=$sth-fetchall_arrayref({});
to get everything all in one go.
--
Peter Haworth [EMAIL PROTECTED]
"Master, does Emacs have the Buddha nature?" the novice asked.
The Chief Priest had been in the temple for
umentation.
--
Peter Haworth [EMAIL PROTECTED]
"You're not going to watch the eclipse in yesterday's underpants?"
,
internallength=9, externallength=9,
element='char'
)
then insert a row to pg_opclass, after attempting to use the new type to find
its ID.
Surely there's an easier way?
--
Peter Haworth [EMAIL PROTECTED]
"Never tell people how to do things.
Tell them WHAT
15 matches
Mail list logo