Reply: Reply: Can we specify transaction level when connectting toexternal postgresql server via postgres_fdw

Поиск
Список
Период
Сортировка
От guxiaobo1982
Тема Reply: Reply: Can we specify transaction level when connectting toexternal postgresql server via postgres_fdw
Дата
Msg-id tencent_20238EDF71186C583E022402@qq.com
обсуждение исходный текст
Список pgsql-general
Greeplum is based on 8.2.15, so we can only use the read-only option.


------------------ Original ------------------
Sender: "Tom Lane"<tgl@sss.pgh.pa.us>;
Send time: Tuesday, Jul 16, 2013 1:57 PM
To: "guxiaobo1982"<guxiaobo1982@qq.com>;
Cc: "Jov"<amutu@amutu.com>; "pgsql-general"<pgsql-general@postgresql.org>;
Subject: Re: Reply: [GENERAL] Can we specify transaction level when connectting toexternal postgresql server via postgres_fdw

"guxiaobo1982" <guxiaobo1982@qq.com> writes:
> It works for insert and select statement under serializable level, but it seems update/delete statements are not support, is that true?
> template1=# update user_info set info='1234' where id=102;
> ERROR:  DECLARE CURSOR ... FOR UPDATE/SHARE is not supported
> DETAIL:  Cursors must be READ ONLY.

The postgres_fdw documentation says

postgres_fdw can be used with remote servers dating back to
PostgreSQL 8.3. Read-only capability is available back to 8.1.

I don't recall exactly when Greenplum forked off from Postgres, but
8.1 or so wouldn't surprise me.  The quoted error message looks about
like what you'd get when trying to use postgres_fdw with a pre-8.3
remote server.

regards, tom lane
.

В списке pgsql-general по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Reply: Can we specify transaction level when connectting toexternal postgresql server via postgres_fdw
Следующее
От: Raghavendra
Дата:
Сообщение: Re: Reply: [GENERAL] 回复: [GENERAL] Can't create plpython language