ight make it easier to understand the
code flow in case you want to examine them.
Cheers
On Thu, Sep 24, 2009 at 9:41 AM, Xavier Noguer wrote:
> Tatsuo,
>
> Our test case was this: two backends running postgres 8.1; a few
> differences between them, with the master node always having more
Tatsuo,
I'm attaching a single patch with both of the changes I sent
previously. It was made against the V2_2_STABLE branch (not HEAD),
because it depends on the patch from Sep 23 11:39:10.
Thanks for all your patience.
Cheers
On Fri, 2009-09-25 at 21:23 +0900, Tatsuo Ishii wrote:
> > Hi
Hi,
Got different problem with DEALLOCATED then other one here. After few
hours (4-5h) normal working start see alot DEALLOCATED process at
pgpool and all db backends got such errors.
#v+
STATEMENT: DEALLOCATE "pdo_pgsql_stmt_8036eec4"
ERROR: prepared statement "pdo_pgsql_stmt_8063113c" does no
That error usually appears when there's a difference between backends.
You should compare the number of affected rows on each backend. If the
query you are running is:
UPDATE table SET field1=’something’ WHERE field2=’something_else’;
then you should run:
SELECT COUNT(*) FROM table WHERE fie
I just try to
> keep making the same update, and every time pgpool complains, instead of
> degenerate the backends and carry on with only backend0.
>
> Any other idea?
>
> Thanks,
> Daniel
>
> > -Original Message-
> > From: Xavier Noguer [mailto:
Hi,
I have pgpool setup with two backends, and every now and then one of
them seems to close a conection to the pgpool server triggering this:
2009-11-15 09:35:53 DEBUG: pid 9334: waiting for master completing the query
2009-11-15 09:35:53 DEBUG: pid 9334: detect_error: kind: E
2009-11-15 09:3
Hello,
I encountered a problem with a pgpool installation. Pgpool failed and
detached a backend, but I don't know the reason because that particular
pgpool server is not writing to its log (problem with cronolog, and I
can't restart pgpool since its a live system).
What I did find was a suspi
I think the number of total connections is num_init_children *
max_pool. In your case that is 60 * 4 = 240 connections.
I also see that you have max_connections = 128 in your postgres
configuration, which means your backend will not allow 240 connections
to be opened to it and pgpool might free
ype 4" which closes the
session and the connection to the client. That would explain why the
pool_read call on pgpool fails, but I still can't figure out why does
the backend receive that invalid message.
Regards
On Thu, Dec 24, 2009 at 11:38 AM, Xavier Noguer
wrote:
>
> Hello,
mit on the postgres log of the failed backend,
> > followed by the "invalid frontend message type 4" which closes the
> > session and the connection to the client. That would explain why the
> > pool_read call on pgpool fails, but I still can't figure out why doe
Hi,
I found what I think is a small error allocating memory in the
make_persistent_db_connection() function in child.c. The amount of
memory allocated is more than it should be, so it's actually harmless.
I attach a patch for it.
Regards
Index: child.c
===
d failed (Connection
> > > > reset by peer)
> > > > 2009-12-26 00:13:04 LOG: pid 16329: notice_backend_error: 1 fail over
> > > > request from pid 16329
> > > >
> > > >
> > > > I can see the commit on the postgres log o
ead: read failed (Connection
> > > > reset by peer)
> > > > 2009-12-26 00:13:04 LOG: pid 16329: notice_backend_error: 1 fail over
> > > > request from pid 16329
> > > >
> > > >
> > > > I can see the commit on the postgres lo
Hello Ger,
I'm not familiar with the package you are using, but pgpool is usually
started by a script which is in /etc/pgpool/scripts/pgpool.sh regardless
of whether this script reads options from some other location.
Pgpool writes its log to standard error by default so you should check
this
Fernando, you can find a description of all message types here:
http://developer.postgresql.org/pgdocs/postgres/protocol-message-formats.html
'D' means is a data row message.
Regards
On Thu, 2010-01-14 at 09:56 -0200, Fernando Morgenstern wrote:
> Hello,
>
>
> Is there a part of the manu
Most of those warnings have already been fixed in cvs by Tatsuo. You
should try checking out the latest version from cvs.
Regards
On Thu, 2010-01-14 at 14:13 +, Glyn Astill wrote:
> Hi people,
>
> Bar the usual bison ones, I've noticed the list of compile time warnings
> getting lager i
>
> Do you any idea of what could have caused it?
>
> I searched postgres log at node 0, trying to find some clue of what happened,
> but there isn't anything there.
>
> Best Regards,
> ---
>
> Fernando Marcelo
> www.consultorpc.com
> ferna...@co
Hi,
> 2010-01-21 14:31:56 ERROR: pid 10881: connection to
> 192.168.101.214(5432) failed
> 2010-01-21 14:31:56 ERROR: pid 10881: new_connection: create_cp()
> failed
> 2010-01-21 14:31:56 LOG: pid 10881: notice_backend_error: 1 fail
> over
> request from pid 10881
this seems to indicate the
18 matches
Mail list logo
