Thank you!
Tena
-Original Message-
From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
Sent: Fri 11/9/2007 4:29 PM
To: Tena Sakai
Cc: Tom Lane; Scott Marlowe; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] idle in transaction...unexpected EOF on clientconnection
Tena Sakai escribió
Tena Sakai escribió:
> Aside from that, can this be caused by many deleted
> rows from tables (and having neglected to vacuum)?
No.
--
Alvaro Herrerahttp://www.advogato.org/person/alvherre
Major Fambrough: You wish to see the frontier?
John Dunbar: Yes sir, before it's g
be caused by many deleted
rows from tables (and having neglected to vacuum)?
Tena Sakai
([EMAIL PROTECTED])
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Fri 11/9/2007 3:03 PM
To: Scott Marlowe
Cc: Tena Sakai; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] idle in
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> Hmmm. Well, when you see an error like unexpected EOF on client
> connection then that means that the client "disappeared" without
> closing the connection, or the network connection went away.
More specifically, the client didn't send the expected "t
On Nov 9, 2007 4:36 PM, Tena Sakai <[EMAIL PROTECTED]> wrote:
> Hi Scott,
>
>
> > Most likely what is happening is that you have a firewall between your
> > app and your db server that is closing idle connections after x minutes.
>
> Thanks for your comment.
>
> I hate to be disagreeable, but
ct: Re: [ADMIN] idle in transaction...unexpected EOF on client connection
On Nov 9, 2007 3:58 PM, Tena Sakai <[EMAIL PROTECTED]> wrote:
>
> Hi Everybody,
>
> I see in serverlog many entries that read:
> LOG: unexpected EOF on
> client connection
> LOG: unexpected E
On Nov 9, 2007 4:29 PM, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Campbell, Lance wrote:
> > I notice this in my log file as well. I do not have a fire wall that
> > would impact this.
>
> It could be a monitoring tool that's opening the socket to check whether
> Postgres is listening. If it co
Campbell, Lance wrote:
> I notice this in my log file as well. I do not have a fire wall that
> would impact this.
It could be a monitoring tool that's opening the socket to check whether
Postgres is listening. If it connects then closes the socket without
actually talking the PG protocol, this
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tena Sakai
Sent: Friday, November 09, 2007 3:58 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] idle in transaction...unexpected EOF on client
connection
Hi Everybody,
I see in serverlog many entries that read:
LOG: unexpected EOF
on client
On Nov 9, 2007 3:58 PM, Tena Sakai <[EMAIL PROTECTED]> wrote:
>
> Hi Everybody,
>
> I see in serverlog many entries that read:
> LOG: unexpected EOF on
> client connection
> LOG: unexpected EOF on
> client connection
> LOG: unexpected EOF on
> client connection
> LOG: unexpected EOF on
Hi Everybody,
I see in serverlog many entries that read:
LOG: unexpected EOF on
client connection
LOG: unexpected EOF on
client connection
LOG: unexpected EOF on
client connection
LOG: unexpected EOF on
client connection
This occurs regularly and frequently and I am
wondering if it is
On Wed, 2006-04-19 at 13:51, Rodrigo Sakai wrote:
> >No problem really, all it means is the application has issued a start
> of transaction command, it just isn’t doing anything at the moment.
>
>
> >Transactions allow any data added during the application’s running to
> be rolled back should, fo
>No problem really,
all it means is the application has issued a start of transaction command, it
just isnt doing anything at the moment.
>Transactions
allow any data added during the applications running to be rolled back should,
for example, the application crash itll prevent half-wr
connection idle, but dont leave it idle in a
transaction.
-Chandra Sekhar Surapaneni
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rodrigo
SakaiSent: Wednesday, April 19, 2006 7:00 AMTo:
pgsql-admin@postgresql.orgSubject: [ADMIN] IDLE IN
TRANSACTION
Hi,
I have an app
Rodrigo Sakai wrote:
> But I want to know if this kind of connection (idle in
> transaction) can cause locks and deadlocks on the db?
Certainly. Make sure the application is closing the transactions
quickly.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
To: pgsql-admin@postgresql.org
Subject: [ADMIN] IDLE IN TRANSACTION
Hi,
I have an app developed with Delphi,
and when I just start tha app it start a process (a connection) on the db
server and the status stay 'IDLE IN TRANSACTION' until the end of the applicatio
Hi,
I have an app developed with Delphi, and
when I just start tha app it start a process (a connection) on the db
server and the status stay 'IDLE IN TRANSACTION' until the end of the
application. The app is developed by other people and I don't know much about
how it was programmed!
"Marc Mitchell" <[EMAIL PROTECTED]> writes:
> So long as the idled transaction isn't holding any locks on any data
> resources, I don't know if this condition is a bad thing. It would be
> nice to be able to differentiate between a transaction that has been
> "declared" but has yet to really begin
olutions, Inc.
Downers Grove, IL 60515
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Warren Little
Sent: Sunday, February 15, 2004 10:24 AM
To: [EMAIL PROTECTED]
Subject: [ADMIN] idle in transaction
We recently upgraded postgres from 7.3
Just a very quick thought, have You issued a:
connection.commit();
Regards,
Søren,
Subject:[ADMIN] idle in transaction
From: Warren Little <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date sent: Sun, 15 Feb 2004 09:23:32 -0700
We recently upgraded postgres from 7.3 to 7.4, along with the JDBC jar,
and noticed all the backend processes/connections are left in the "idle
in transaction" state where before they where left in the "idle" state.
Has something changed in the 7.4 jdbc driver vs 7.3 which might be
causing this?
No
On Fri, Oct 04, 2002 at 08:04:37PM +0530, [EMAIL PROTECTED] wrote:
> I too use mod_perl + postgresql
> its perfectly ok to have "idle in transaction..."
Well, not really. But it's probably normal. See below.
> the persistant connections makes all the difference.
For some reason, most of the p
Hey Kotis!
I too use mod_perl + postgresql
its perfectly ok to have "idle in transaction..."
Becoz as soon as DBI -> commits a given transaction the
mod_perl process starts a new transaction. the $dbhs' are
in a perpetual transaction mode.
I gues you must have done DBI->{AutoCommit} = 0 fo
Hi all.
Let me start by saying that I've been using postgres 7.1.3 since it came out
and have found it to be rock solid and simply wonderful! :-)
I particularly like the unlimited size varchars which I was waiting like
crazy for. ( actually i think they came out in a previous release which i
m
24 matches
Mail list logo
