Re: "Multiple statements are an issue with pgPool-II in its replication mode" again

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: TAKATSUKA Haruka <harukat(at)sraoss(dot)co(dot)jp>, pgadmin-support(at)postgresql(dot)org
Subject: Re: "Multiple statements are an issue with pgPool-II in its replication mode" again
Date: 2010-11-25 09:09:15
Message-ID: 4CEE27BB.5060300@lelarge.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Le 25/11/2010 09:41, Dave Page a écrit :
> On Thu, Nov 25, 2010 at 7:57 AM, Guillaume Lelarge
> <guillaume(at)lelarge(dot)info> wrote:
>>
>> I don't really understand. These do not come from pgAdmin, right?
>> because we don't filter pg_enum by oid. We sort by oid for pg_enum (and
>> there's no way to do otherwise before 9.1), but we don't filter by oid.
>> So this example should be working (once you're connected, which is your
>> main issue IIRC).
>
> Maybe not, but we do use OIDs in a bunch of places where things will
> break if pgPool returns results from a different server - for example,
> for refreshing a single object we often do something like:
>
> type = typeFactory.CreateObjects(coll, 0, wxT("\n AND t.oid=") + GetOidStr());
>
> Fixing all those instances would take some work, but would at least be
> feasible.

Actually, I don't see how you can do that. The OIDs are used there as a
unique identifier for this object.

> What I don't see an easy fix for, is that we also use xmin
> to detect external changes to some object types.

You mean for functions? yeah, that would be another issue.

--
Guillaume
http://www.postgresql.fr
http://dalibo.com

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Guillaume Lelarge 2010-11-25 09:12:28 Re: pgagent (3.0.0 linux tarball) looking for libssl.so.0 and libcrypto.so.0
Previous Message Dave Page 2010-11-25 08:41:06 Re: "Multiple statements are an issue with pgPool-II in its replication mode" again