Hi,
-- [EMAIL PROTECTED] wrote:
> So this means, If client does never try to send data the
> resources would be going to be held.
> I think it is not a good solution to find zombie / dead
> connection and clear them..
With TCP/IP you DON'T have any other options then waiting for a timeout. In
Hi,
-- Dennis Bjorklund <[EMAIL PROTECTED]> wrote:
> The tcp hackers have provided an api for clients to set these values per
> socket (setsockopt with TCP_KEEPIDLE and similar (in linux at least)).
you can use SO_KEEPALIVE:
[...] SO_KEEPALIVE enables
the periodic transmission of messages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -- Shachar Shemesh <[EMAIL PROTECTED]> wrote:
> The new requirement encapsulates the original requirement, and your
> license is therefor not violated. I have, in fact, relicensed your work.
no, the license is only for the *combined* work (which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
- -- [EMAIL PROTECTED] wrote:
> I would say this is a clear 'NO!' When ever I read about open-source being
> used anywhere, I always read MySQL. They are *very* good at this.
yes!
Some days ago, there was a news in the Heise Newsticker (most imp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
- -- Bruce Momjian <[EMAIL PROTECTED]> wrote:
> o Are we marketing ourselves properly?
while talking about MySQL, there is the myth, that MySQL is fast; and that
because MyISAM has no transactions, that it is faster.
That is in most case
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
- -- Joe Conway <[EMAIL PROTECTED]> wrote:
> Please try the attached patch and let me know how it works for you. It is
> against cvs HEAD, but should apply OK to 7.4.
so, I checked it with my database.
It looks good, all checks I made are OK.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -- Joe Conway <[EMAIL PROTECTED]> wrote:
> Well, 7.4.1 will be bundled up for release on Sunday, so it would be
> ideal to get some feedback sooner if possible.
this is a good argument ... ;)
I'll try to check it ...
Ciao
Alvar
- --
** Alv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Joe,
- -- Joe Conway <[EMAIL PROTECTED]> wrote:
> Please try the attached patch and let me know how it works for you. It is
> against cvs HEAD, but should apply OK to 7.4.
has this about one week time? I travel on monday to Geneva (World Summit o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
- -- Joe Conway <[EMAIL PROTECTED]> wrote:
> I understand the root cause,
> but am still trying to figure out what the "right" solution is. It may
> take another day or so due to other things I have going on (like my job
> ;-)).
:-)
If you need
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
- -- Joe Conway <[EMAIL PROTECTED]> wrote:
> Apparently you never read my reply to you all the way to the bottom. I
> said:
oh, sorry, I understand your mail wrong!
I understand it in this way, that you are not sure that there is something
buggy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
while changing a column from base255 encoded text (all except null byte) to
bytea, I found the following bug in Postgresql's LIKE operator with indexes
(it follows a more detailed description then my old mails in -bugs and
- -general, including th
Hi,
-- [EMAIL PROTECTED] wrote:
> What about checking the input for backslash, quote,
> and double quote (\'")? If you are not taking care of those in input
> then crashing the backend is going to be the least of your worries.
with Perl and *using placeholders and bind values*, the applica
Thomas Lockhart wrote:
>
> The parser does not know that your int4 constant "0" can be represented
> as an int2. Try
>
> SELECT * FROM access_log WHERE method_num = int2 '0';
hmmm, but its still a sequentiell scan:
logger=# explain SELECT * FROM access_log
WHER
Hi,
I have the following table, containing about 57 Rows, but some
indexes are not used, on 7.1RC4, freshly vacuumed (analyse). It was the
same at least in 7.1RC1
--- SNIP ---
CREATE TABLE access_log(
site_id int2NOT NULL DEFAULT 0,
access_time timestam
14 matches
Mail list logo
