later, I'd like
to get it fixed now.
Thanks in advance,
Jim Wilson
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
must be working really well since you have the
time
to litter my inbox with all these trivial arguments. :-)
BTW who was the EXPERT that slammed java performance?
Best regards,
Jim Wilson
--
Jim Wilson
Kelco Industries
PO Box 160
Milbridge, ME 04658
207-546-7989
-Original Message-
From: Tony Caduto
One example is LimeWire, while it works well, it takes forever to load and
Six seconds on mine.
Best regards,
Jim Wilson
--
Jim Wilson
Kelco Industries
PO Box 160
Milbridge, ME 04658
207-546-7989
---(end
and easy maintenance for very low per user cost as compared to
just about anything else.
You may want to contact the folks at this web address for local linux support.
http://nglug.org/
In any case I wish you the best of luck in your business.
Best regards,
Jim Wilson
becoming memory
bound (e.g. not enough RAM or poor garbage collection/memory leakage on the
client side)?
Best regards,
Jim Wilson
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
not want to debate the
meaning
of the word instability. :-)
Best regards,
Jim Wilson
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send unregister YourEmailAddressHere to [EMAIL PROTECTED])
harder, and
if I were, this
problem would be at the top of my list as things to fix in Postgres.
Best regards,
Jim Wilson
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
Jim Wilson [EMAIL PROTECTED] writes:
If you are not very careful about how you handle orphaned
connections
in Postgres you will likely lose datanot maybe like a long
shot...but likely.
[ raised eyebrow ... ] Say again? I don\'t know of any reason why a
lost connection would cause
Jim Wilson [EMAIL PROTECTED] writes:
Rather than getting into the raised eyebrow thing , I\\\'d
suggest
checking your qualifiers. Consider that with Postgres, if killing
a
single connection brings the whole server down, you will loose
_all_
uncommitted data. If you did not, then I
On Fri, Feb 04, 2005 at 05:01:43PM -0500, Jim Wilson wrote:
Rather than getting into the raised eyebrow thing , I\\\'d
suggest
checking your qualifiers. Consider that with Postgres, if killing
a
single connection brings the whole server down, you will loose
_all_
uncommitted data
idea. I have not used the stored procedure statement object as you did.
Perhaps that would be more portable.
Best,
Jim
--
Jim Wilson - IT Manager
Kelco Industries
PO Box 160
58 Main Street
Milbridge, ME 04658
207-546-7989 - FAX 207-546-2791
http://www.kelcomaine.com
Clark Endrizzi said:
I just sent this twice before with the wrong email address so it didn't
go through, that is why I am sending this so that it will get through.
I hope this isn't causing issues.
Hi guys. I certainly hope this is the correct place to email this. I'm
having an issue
David Garamond said:
Bruce Momjian wrote:
So can I quietly beg the Win32 group to expedite this port. I believe
you will be utterly astonished at the demand. Please.
Speaking of win32 port, do/will we need a win32 users list
(pgsql-win32)? MySQL has one. For now, I think such a list
cause similar issues in a system with tons of ram and cpu.
Best,
Jim
--
Jim Wilson - IT Manager
Kelco Industries
PO Box 160
58 Main Street
Milbridge, ME 04658
207-546-7989 - FAX 207-546-2791
http://www.kelcomaine.com
---(end of broadcast)---
TIP 6
is/will be tackled on Win32 port).
It seems like you could handle all the above with just a shell script wrapper.
All three, the library path, socket directory, and data directory can be
specified either in environment or on the command line. Where are you getting
stuck?
Best,
Jim Wilson
://pbpgsql.spiderbark.com
Best regards,
Jim Wilson
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
not just use a text type in your definition?
CREATE or REPLACE FUNCTION use_two_tables(text) RETURNS text AS ...
You can always do a cast inside the procedure if you need to.
Best regards,
Jim Wilson
---(end of broadcast)---
TIP 5: Have you
Stephan Szabo [EMAIL PROTECTED] said:
On Mon, 12 Jan 2004, Tom Lane wrote:
Jim Wilson [EMAIL PROTECTED] writes:
As far as I can tell, there isn't a way to get postgresql to accept column
qualifiers (e.g. tablenames). A 'parse error at or near .' gets returned.
You're either very
Tom Lane [EMAIL PROTECTED] said:
Jim Wilson [EMAIL PROTECTED] writes:
As far as I can tell, there isn't a way to get postgresql to accept column
qualifiers (e.g. tablenames). A 'parse error at or near .' gets returned.
You're either very confused or using a *very* old version of Postgres
19 matches
Mail list logo
