From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
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 08:41:06 |
Message-ID: | AANLkTik1_Jc2q3CrB1gTY57s+jy8d8Vg-jAsb1SDGOfv@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
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. What I don't see an easy fix for, is that we also use xmin
to detect external changes to some object types.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2010-11-25 09:09:15 | Re: "Multiple statements are an issue with pgPool-II in its replication mode" again |
Previous Message | Guillaume Lelarge | 2010-11-25 07:57:40 | Re: "Multiple statements are an issue with pgPool-II in its replication mode" again |