Re: "Multiple statements are an issue with pgPool-II in its replication mode" again
От | Dave Page |
---|---|
Тема | Re: "Multiple statements are an issue with pgPool-II in its replication mode" again |
Дата | |
Msg-id | AANLkTik1_Jc2q3CrB1gTY57s+jy8d8Vg-jAsb1SDGOfv@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: "Multiple statements are an issue with pgPool-II in its replication mode" again (Guillaume Lelarge <guillaume@lelarge.info>) |
Ответы |
Re: "Multiple statements are an issue with pgPool-II
in its replication mode" again
|
Список | pgadmin-support |
On Thu, Nov 25, 2010 at 7:57 AM, Guillaume Lelarge <guillaume@lelarge.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
В списке pgadmin-support по дате отправления: